On Thu, Nov 27, 2008 at 02:47:44PM -0500, Mike Frysinger wrote:
> if you specify journal=update in /etc/fstab, then attempts to remount that
> point can be a bit painful
>
> for example:
> dd if=/dev/zero of=foo count=10000
> mke2fs -F -j foo
> mkdir foo-mount
> echo $PWD/foo $PWD/foo-mount ext3 defaults,loop,journal=update >> /etc/fstab
> mount foo-mount
> mount foo-mount -o remount,ro
>
> the last command will result in:
> mount: /root/foo-mount not mounted already, or bad option
this is a generic remount EINVAL error message
> and the dmesg output will show us:
> EXT3-fs: cannot specify journal on remount
>
> so should mount be handling this ?
How do you want to handle this in mount(8)? It's fs-depend option and
all is this behaviour is managed by kernel.
> or should we update ext3 to only abort if the journal= option given
> at remount is different from the initial mount ?
... CC: linux-fs or linux-ext4 list ?
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
