linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Parnell <mparnell@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: Bug In ext4 in kernels > 2.6.39 - Not mounting with arguments/options I specify in fstab on root remount
Date: Tue, 13 Sep 2011 04:01:04 -0500	[thread overview]
Message-ID: <CABeR262=5V1wuXPDVr_qLTeFTc4zDSFKVYKvO_+1w60XmwJvKA@mail.gmail.com> (raw)
In-Reply-To: <4E6F1B49.3010803@gmail.com>

Hi all... I usually run my system the zen kernel (zen-kernel.org), but
I've tried this with the default Archlinux kernel (pretty much a
vanilla build) as well and for some reason, the root drive won't mount
with the options I desire on anything above .29 The drive is an SSD,
and this is really getting on my nerves. I've looked at the
initscripts, fstab, everything else, and I just can't get any of this
to work properly. It was mounting with all the options I specified in
2.6.39, but since some change to the kernel (or something else?) I
can't mount with my options anymore. On top of this all, I've tried
using both /dev/root and /dev/sdb1, but for some reason the kernel's
only wanting to use /dev/root - I'm wondering if there's some kind of
conflict due to that symlink...

I know this isn't my initscripts, as I've also tried this using
openrc, aside from the default arch init system, and because upon
downgrading to 2.6.39 everything is working normally again, I know it
is the kernel. Information:

grub.cfg:

linux	/boot/linux-zen root=/dev/sdb1 ro rootfstype=ext4
rootflags=data=writeback noatime barrier=0 discard noinitrd

fstab:

/dev/sdb1 / ext4 data=writeback,noatime,nodiratime,barrier=0,discard 0 1

Upon attempting to remount manually, I only get the following when I
try to use the options I specified above:

EXT4-fs (sdb1): Cannot change data mode on remount

Interestingly, this also happened and worked, which I think is a bug,
how can barrier=0 and 1 at the same time?

EXT4-fs (sdb1): re-mounted. Opts: user_xattr,barrier=1,barrier=0

I'm currently using a .39 kernel and can live with it for now, but I
thought this was serious enough that the ext4 devs should hear about
it. If you need any more information, just let me know.

Thanks!

Matt Parnell

       reply	other threads:[~2011-09-13  9:07 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 ` Matt Parnell [this message]
2011-09-13 10:25   ` Bug In ext4 in kernels > 2.6.39 - Not mounting with arguments/options I specify in fstab on root remount 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
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='CABeR262=5V1wuXPDVr_qLTeFTc4zDSFKVYKvO_+1w60XmwJvKA@mail.gmail.com' \
    --to=mparnell@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    /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).