From: Matt Parnell 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 02:53:34 -0500 Message-ID: <4EA2767E.2080509@gmail.com> References: <4E6F1B49.3010803@gmail.com> <4E6F6D89.5040905@redhat.com> <20111009234433.GU7948@thunk.org> <4EA0E72D.8020305@gmail.com> <20111022050031.GC4196@thunk.org> <4EA27607.20407@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Eric Sandeen , linux-ext4@vger.kernel.org To: Ted Ts'o Return-path: Received: from mail-iy0-f174.google.com ([209.85.210.174]:65269 "EHLO mail-iy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751883Ab1JVHxi (ORCPT ); Sat, 22 Oct 2011 03:53:38 -0400 Received: by iaek3 with SMTP id k3so5643766iae.19 for ; Sat, 22 Oct 2011 00:53:38 -0700 (PDT) In-Reply-To: <4EA27607.20407@gmail.com> Sender: linux-ext4-owner@vger.kernel.org List-ID: Also, I didn't intend to come across cross there... I appreciate the efforts you are taking there. It's just, I don't know what could've changed between .29 and 3.0 that would break an entire init system so that it won't remount root rw... On 10/22/2011 02:51 AM, 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... > > This is all a big wtf though. I'm going to go complain at the arch > devs now... I've not finished porting openrc to it yet. > > On 10/22/2011 12:00 AM, Ted Ts'o wrote: >> 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