You are not logged in.

#1 2011-09-09 07:23:32

ilikenwf
Member
Registered: 2008-06-23
Posts: 42
Website

ext4 not using arguments/options I specify in fstab or grub.cfg

Hi all... I run the zen kernel, but I've tried this with the arch kernel as well and for some reason, the root drive won't mount with the options I desire. The drive is an SSD, and this is really getting on my nerves. I've looked at the initscripts, fstab, everything else, and I just can't get any of this to work properly. It was mounting with all the options I specified sometime before the transition to kernel 3.0, but since some change to the kernel (or something else?) I can't mount with my options anymore. On top of this all, I've tried using /dev/root and /dev/sdb1, but for some reason the kernel's only wanting to use /dev/root - I'm wondering if there's some kind of conflict due to that symlink...


grub.cfg options (yes, this happens with the Arch kernel too):

linux	/boot/linux-zen root=/dev/sdb1 ro rootfstype=ext4 rootflags=data=writeback noatime nodiratime barrier=0 discard noinitrd

fstab:

/dev/sdb1 / ext4 data=writeback,noatime,nodiratime,barrier=0,discard 0 1

Playing around remounting manually, I only get the following when I try to use the options I specified above.

EXT4-fs (sdb1): Cannot change data mode on remount

Interestingly, this also happened and worked, which I think is a bug, how can barrier=0 and 1 both?

EXT4-fs (sdb1): re-mounted. Opts: user_xattr,barrier=1,barrier=0

Whatever the case, would any of you mind helping me figure this out?

Last edited by ilikenwf (2011-09-09 07:25:12)

Offline

#2 2011-09-11 09:00:16

rwd
Member
Registered: 2009-02-08
Posts: 664

Re: ext4 not using arguments/options I specify in fstab or grub.cfg

Does 'cat /proc/mounts' give the same info as mtab?  Could it be that mtab isn't up-to date?

Offline

#3 2011-09-11 09:25:00

ilikenwf
Member
Registered: 2008-06-23
Posts: 42
Website

Re: ext4 not using arguments/options I specify in fstab or grub.cfg

I think mtab is up to date, but can't check now because I rolled back my kernel. I don't think it's the Arch initscripts either, as it happened with both arch and the zen kernels at >= 3.0. I rolled back and built a 2.6.39 kernel and it all works, so I'll be filing an ext4 bug report tomorrow on the kernel bugzilla.

Offline

Board footer

Powered by FluxBB