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 01:00:31 -0400 [thread overview]
Message-ID: <20111022050031.GC4196@thunk.org> (raw)
In-Reply-To: <4EA0E72D.8020305@gmail.com>
On Thu, Oct 20, 2011 at 10:29:49PM -0500, Matt Parnell wrote:
> The output of /proc/cmdline on 3.0.7:
>
> BOOT_IMAGE=/boot/vmlinuz26-zen root=/dev/sdb1 ro rootfstype=ext4
> rootflags=data=writeback noatime nodiratime barrier=0 discard
> noinitrd
>
>
> On 10/09/2011 06:44 PM, Ted Ts'o wrote:
> >On Sun, Oct 09, 2011 at 05:10:54PM -0500, Matt Parnell wrote:
> >>/proc/mounts (as you can see it's not being remounted rw for some
> >>reason - /dev/sdc1 is the flash drive I used to pipe this info onto):
> >>
> >>rootfs / rootfs rw 0 0
> >>/dev/root / ext4 ro,relatime,barrier=1 0 0
I haven't had a chance to check on v3.0 (I'm currently travelling and
penning this from an airplane), but on v3.1-rc3, it works for me under
KVM. I fire up kvm-qemu this way:
$QEMU -enable-kvm -boot order=c $NET \
-drive file=$ROOT_QCOW2,if=virtio$SNAPSHOT \
-drive file=$VDB,cache=none,if=virtio \
-drive file=$VDC,cache=none,if=virtio \
-drive file=$VDD,cache=none,if=virtio \
-nographic -smp $NR_CPU -m $MEM \
--kernel $KERNEL \
--append "root=/dev/vda console=ttyS0,115200 rootflags=data=writeback" |\
tee $LOGFILE
with this in /proc/cmdline:
candygram:~# cat /proc/cmdline
root=/dev/vda console=ttyS0,115200 rootflags=data=writeback maint
... and this is what I have in /proc/mounts:
candygram:~# head -2 /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext4 rw,noatime,user_xattr,acl,barrier=1,data=writeback 0 0
... and what I have in /etc/fstab:
UUID=ce4d6b98-2aa9-42d4-a127-995a795a0b02 / ext4 noatime,data=writeback 0 1
The kvm image I'm using is using Debian unstable image generated using
debootstrap, and uses no modules or initrd's --- which makes it easier
for me to boot since $KERNEL is set to:
/tyt/linux/ext4/arch/x86/boot/bzImage
This allows me to fire up test kernel right from my build tree,
without needing to set up any kind of initrd nonsense. :-)
- Ted
next prev parent reply other threads:[~2011-10-22 7:49 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 [this message]
2011-10-22 7:51 ` Matt Parnell
2011-10-22 7:53 ` Matt Parnell
2011-10-22 9:32 ` Ted Ts'o
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=20111022050031.GC4196@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).