[<prev] [next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.01.1109130346210.9183@trent.utfs.org>
Date: Tue, 13 Sep 2011 03:48:10 -0700 (PDT)
From: Christian Kujau <lists@...dbynature.de>
To: Matt Parnell <mparnell@...il.com>
cc: linux-ext4@...r.kernel.org
Subject: Re: Bug In ext4 in kernels > 2.6.39 - Not mounting with arguments/options
I specify in fstab on root remount
[ Cc'ing linux-ext4 again ]
On Tue, 13 Sep 2011 at 05:44, Matt Parnell wrote:
> > Did you try booting with init=/bin/bash, i.e. bypassing all initscripts?
> > Also, try booting w/o an initrd image if you can, thus bypassing all the
> > early boot magic.
>
> Not exactly, but I had it drop out to perform an fsck, and the mtab
> indicated it was mounted according to my options, but this was when
> the disk was mounted read only from grub. Also, I don't use an
> initrd...so that's not it either.
Yeah, mtab is no good when your rootfs is readonly. What did /proc/mounts
say?
C.
> > Shot in the dark: if it worked with 2.6.39 but not with 3.x and the
> > initscript have not changed, maybe some initscript went mad when it
> > could not parse the new kernel version number?
> >
> > Christian.
>
> It's not that either... Arch has been using 3.0+ as it's default for a
> few weeks now, so they would've updated their scripts for that.
> Furthermore, I tried using OpenRC (the gentoo init system) and got the
> same results.
>
--
BOFH excuse #359:
YOU HAVE AN I/O ERROR -> Incompetent Operator error
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists