You are not logged in.
I just had a strange problem, supposedly due to today's update.
I rebooted and ended up with a read-only root filesystem, thousands of 'cannot remove /tmp/xy', 'mount' showed it as 'ro' etc., thus no X, KDE etc.
Of course I didn't have that option in fstab, it seemed all normal in there.
I noticed there was 'reservation' mentioned somewhere in the booting process, and found it in my fstab's entry for root.
Removing it (luckily I had an Arch live disc at hand) got me my read-write root fs back.
So now there's no issue anymore, I just want to understand where all this came from. Is it not supported anymore?
I didn't find much on it on the internet, just that it's supposed to somehow improve performance a bit (which is probably why I added it, cannot remember that though).
Thanks,
EdgarButan
Last edited by EdgarButan (2012-02-26 00:05:29)
Offline
It seems that enabling CONFIG_EXT4_USE_FOR_EXT23 in recent kernel makes this option impossible. Grepping through the kernel source, it was only ever supported for ext3.
Just to confirm: you don't have testing enabled, correct?
Last edited by falconindy (2012-02-25 00:43:06)
Offline
Was this with the update to util-linux 2.21 or could you still observe it with 2.20 (but with the newest kernel)?
Offline
@Edgar: i posted a fix to the ext4 list, so let's see what the experts say: http://news.gmane.org/gmane.comp.file-systems.ext4 :-)
Offline
@falconindy Testing is not enabled, no. All standard Arch kernels etc.
@tomegun
That was fast And it seems like your patch was accepted.
I mean, as I said, I don't even know why I was using that option, so it's not critical for me to get this fixed, but I guess I'm not the only one with that option lurking around and ending up with a read-only root fs is not a nice way to find out about it.
By the way, I'm using util-linux 2.20(.1-2) right now, it's not even been updated.
Will set this thread to SOLVED now, I guess.
Thanks!
Last edited by EdgarButan (2012-02-26 00:03:41)
Offline