All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "Ted Ts'o" <tytso@mit.edu>
Cc: Lukas Czerner <lczerner@redhat.com>,
	Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: don't give the "disabling delalloc" if not explicitly specified
Date: Mon, 15 Aug 2011 15:04:26 -0500	[thread overview]
Message-ID: <4E497BCA.4030300@redhat.com> (raw)
In-Reply-To: <20110815175426.GB5948@thunk.org>

On 8/15/11 12:54 PM, Ted Ts'o wrote:
> On Mon, Aug 15, 2011 at 10:59:02AM -0500, Eric Sandeen wrote:
>>
>> The giant behavior-options switch in ext4 is confusing enough; if enabling
>> one option disables another default option, I think that explicitly stating
>> it in the logs is useful.  Doing so silently just covers up the behavior.
>>
>> If users are unhappy with the message, it's probably more because of 
>> the fact of the matter, and not because of the presentation of the fact.  :)
> 
> Most users probably have no idea what "delalloc" actually means.  So
> when they get a message that saying that data=journalled has disabled
> delalloc, it could easily be seen as noise.  I was moved to do it
> because I got tired of seeing the message over, and over, and over
> again when running xfstests.
> 
> Maybe an improvement would be (1) to document what data=journal
> implies in the Documentation/filesystems/ext4.txt, (2) change the
> message to explicitly say "delayed allocation" instead of "delalloc"
> (although many people won't have any idea what "delayed allocation"
> means either), and (3) make it a printk_once thing.
> 
> I guess I don't agree with the fundamental presumption which is that
> users should be looking at the dmesg output to understand what various
> things mean, and if they didn't explicitly specify delalloc, why
> should we complain about the fact that both delalloc and data=journal
> were specified (when in fact it wasn't specified).

Well, just my $0.02, I won't fight it.

One thing I do want, though, is to be able to look at logs and know
what mode we're running in.  I guess we do print all specified options,
so those in the know, will know that delalloc is off if data=journal is on.

But I think we could use some consistency here at least:

[root@inode ~]# mount -o data=journal,dioread_nolock /dev/sdb5 /mnt/test
[root@inode ~]#  /* YAY it worked! */

[root@inode ~]# dmesg | tail
...
[269530.183245] EXT4-fs (sdb5): Ignoring delalloc option - requested data journaling mode
[269530.191170] EXT4-fs (sdb5): Ignoring dioread_nolock option - requested data journaling mode

/* boo it didn't work */

Better hit that one too, I guess, and any other option which disables
another default ...  (honestly, I think it'd be better to fail the mount
in cases like this if conflicting options are specified).

-Eric


-Eric

  parent reply	other threads:[~2011-08-15 20:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-14  2:52 [PATCH] ext4: don't give the "disabling delalloc" if not explicitly specified Theodore Ts'o
2011-08-15 10:14 ` Lukas Czerner
2011-08-15 15:59   ` Eric Sandeen
2011-08-15 17:54     ` Ted Ts'o
2011-08-15 18:13       ` Lukas Czerner
2011-08-15 20:04       ` Eric Sandeen [this message]
2011-08-16 19:14         ` [PATCH] ext4: improve handling of conflincting mount options Theodore Ts'o

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=4E497BCA.4030300@redhat.com \
    --to=sandeen@redhat.com \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.