From: Ted Ts'o <tytso@mit.edu>
To: Matt Parnell <mparnell@gmail.com>
Cc: Eric Sandeen <sandeen@redhat.com>, linux-ext4@vger.kernel.org
Subject: Re: Bug In ext4 in kernels > 2.6.39 - Not mounting with arguments/options I specify in fstab on root remount
Date: Sat, 22 Oct 2011 05:32:18 -0400 [thread overview]
Message-ID: <20111022093218.GF4196@thunk.org> (raw)
In-Reply-To: <4EA27607.20407@gmail.com>
On Sat, Oct 22, 2011 at 02:51:35AM -0500, Matt Parnell wrote:
> That doesn't really help me at all, it's not
> rootflags=data=writeback causing this, it's starting to make me
> think that arch's init may be to blame, although I previously ruled
> it out...
Well, it looks like rootflags=data=writeback is not making it to the
file system. That's why it's not showing up in /proc/mounts, from you
showed us. Can you look at the kernel dmesg?
You should see something like this:
[ 1.421146] EXT3-fs (vda): error: couldn't mount because of unsupported optional features (240)
[ 1.434057] EXT4-fs (vda): couldn't mount as ext2 due to feature incompatibilities
[ 1.454631] EXT4-fs (vda): mounted filesystem with writeback data mode. Opts: data=writeback
[ 1.455966] VFS: Mounted root (ext4 filesystem) readonly on device 254:0.
The first line is the failure to mount the root file system as ext3.
The 2nd is the failure to mount the file system as ext2, using the
ext4 file system driver. The last two lines show the options show the
mount as ext4.
What do those two lines look to you. If you don't see "Opts:
data=writeback", then somehow the rootflags option isn't getting passed
down to the file system. Then when you try to remount the file system
read/write, the fact that you have "data=writeback" in your /etc/fstab
causes the failure to remount.
If you simply remove that from /etc/fstab, things should work better.
The remount will preserve whatever data=journalling mode was in use
when the root file system was originallymounted as. If rootflags is
non-functional, then the file system won't be mounted as
data=writeback, but at least the boot sequence will continue without
blowing out.
- Ted
next prev parent reply other threads:[~2011-10-22 9:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E6F1B49.3010803@gmail.com>
2011-09-13 9:01 ` Bug In ext4 in kernels > 2.6.39 - Not mounting with arguments/options I specify in fstab on root remount Matt Parnell
2011-09-13 10:25 ` Christian Kujau
[not found] ` <CABeR261eWW1vi1Xk9E6SWdy7PN=oiDbQdT_LiHgZf7+6V7Sv8Q@mail.gmail.com>
2011-09-13 10:48 ` Christian Kujau
2011-09-13 14:49 ` Eric Sandeen
2011-10-09 22:10 ` Matt Parnell
2011-10-09 23:44 ` Ted Ts'o
2011-10-21 3:29 ` Matt Parnell
2011-10-21 4:29 ` Matt Parnell
2011-10-22 5:00 ` Ted Ts'o
2011-10-22 7:51 ` Matt Parnell
2011-10-22 7:53 ` Matt Parnell
2011-10-22 9:32 ` Ted Ts'o [this message]
2011-11-07 2:18 ` Matt Parnell
2011-11-07 2:24 ` Matt Parnell
2011-11-07 5:26 ` Matt Parnell
2011-11-07 5:32 ` Matt Parnell
2011-11-07 15:47 ` Ted Ts'o
2011-11-08 1:48 ` Matt Parnell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111022093218.GF4196@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=mparnell@gmail.com \
--cc=sandeen@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).