| commit | 3c4cec65274481ec6332b0a91f19b4c8c5394801 | |
| author | Jan Kara <jack@suse.cz> | |
| Mon, 24 Aug 2009 14:38:43 +0000 (24 16:38 +0200) | ||
| committer | Jan Kara <jack@suse.cz> | |
| Mon, 24 Aug 2009 14:48:45 +0000 (24 16:48 +0200) | ||
| tree | c74bd4cedaecdf2b1132753ffbc337e8d3e6b161 | treesnapshot (tar.gz zip) |
| parent | 6d41807614151829ae17a3a58bff8572af5e407e | commitdiff |
ext3: Improve error message that changing journaling mode on remount is not possible
This patch makes the error message about changing journaling mode on remount
more descriptive. Some people are going to hit this error now due to commit
bbae8bcc49bc4d002221dab52c79a50a82e7cd1f if they configure a kernel to default
to data=writeback mode. The problem happens if they have data=ordered set for
the root filesystem in /etc/fstab but not in the kernel command line (and they
don't use initrd). Their filesystem then gets mounted as data=writeback by
kernel but then their boot fails because init scripts won't be able to remount
the filesystem rw. Better error message will hopefully make it easier for them
to find the error in their setup and bother us less with error reports :).
Signed-off-by: Jan Kara <jack@suse.cz>
This patch makes the error message about changing journaling mode on remount
more descriptive. Some people are going to hit this error now due to commit
bbae8bcc49bc4d002221dab52c79a50a82e7cd1f if they configure a kernel to default
to data=writeback mode. The problem happens if they have data=ordered set for
the root filesystem in /etc/fstab but not in the kernel command line (and they
don't use initrd). Their filesystem then gets mounted as data=writeback by
kernel but then their boot fails because init scripts won't be able to remount
the filesystem rw. Better error message will hopefully make it easier for them
to find the error in their setup and bother us less with error reports :).
Signed-off-by: Jan Kara <jack@suse.cz>
| fs/ext3/super.c | diffblobblamehistory |