If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

large block device support missing in 3.7.1?

12-18-2012, 06:33 PM

Under the menu heading "Enable the block layer" there should be an option called "Support for large (2TB+) block devices and files" which is required for just about every modern filesystem, but it seems to be missing. Without it, I cant get my / partition to mount r/w....

Am I missing something obvious? I looked all through the menuconfig and couldnt find it. Without that option ext4 is worthless. and I dont know what happened to it.

Any help would be awesome. if you guys need more information I'll gladly get it for you.

EDIT: I know that there are some kernel options that only become visible if some prerequisite is checked, does this option also have a prereq that needs checked for it to be visible?

So if that option is not required for 64bit, then my problem is something entirely different than what I thought. This is a typed out as closely as I could remember of the exact error message dmesg gave me. I cant get a kernel log because the / fs is mounting ro and so it isnt being written to disk.

Comment

well, i did not have those options in my kernel, so i added them and rebuilt it, but i am still getting exactly the same problem.... however according to dmesg devtmpfs is being loaded after the kernel mounts the fs ro..

Comment

I couldnt figure this problem out, so I decided to re-install on the tried and true ext3...... exactly the same problem..... I'm completely stumped. I dont have a useable os, and I have no idea what is wrong so I can fix it.

Comment

I have "rw,errors=remount-ro" for my / disk in fstab, instead of "defaults".
There is also nothing wrong mount it as ro, so long you make relevant directories rw. For example server hardening use that.
But assigning ro to whole / is stupid. Try change this in your fstab.

I don't think tmpfs has anything to do with it.

Comment

There could also be other causes. If you post dmesg somewhere, it could really allow to help you.
Also, you could try compile and boot older kernel with exactly same config and look if it works, just to narrow the issue down.