linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Matt Parnell <mparnell@gmail.com>
Cc: 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: Tue, 13 Sep 2011 09:49:45 -0500	[thread overview]
Message-ID: <4E6F6D89.5040905@redhat.com> (raw)
In-Reply-To: <CABeR262=5V1wuXPDVr_qLTeFTc4zDSFKVYKvO_+1w60XmwJvKA@mail.gmail.com>

On 9/13/11 4:01 AM, Matt Parnell wrote:

> 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

Fairly certain that the parser will just take the last value specified
for the option.

/proc/mounts likely says "nobarrier" when you specify it this way?

-Eric

  parent reply	other threads:[~2011-09-13 14: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 [this message]
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=4E6F6D89.5040905@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mparnell@gmail.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).