From: Eric Sandeen <sandeen@redhat.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Fix ext4_show_options to show the correct mount options.
Date: Wed, 24 Oct 2007 13:25:15 -0500 [thread overview]
Message-ID: <471F8E0B.7070202@redhat.com> (raw)
In-Reply-To: <471F8C67.2020907@linux.vnet.ibm.com>
Aneesh Kumar K.V wrote:
> So my understanding was that we are supposed to make /proc/mounts show the same output as
> /etc/mtab did. In that case should we be showing the the default set in super block ?
>
> -aneesh
Hm, well, it's true that they would not show up in mtab... but to me
it's logical that "default mount options" set via tunefs *should* show
up as options if they are not set to fs defaults. And using
/proc/mounts has the advantage that they *can* show up.
I guess I'm not sure of the pros or cons of either approach. :)
-Eric
next prev parent reply other threads:[~2007-10-24 18:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 16:47 Patches for review Aneesh Kumar K.V
2007-10-24 16:47 ` Aneesh Kumar K.V
2007-10-24 16:47 ` Aneesh Kumar K.V
2007-10-24 16:47 ` [PATCH] ext4: Change the default behaviour on error Aneesh Kumar K.V
2007-10-24 16:47 ` [PATCH] ext4: Fix mballoc BUG when running compilebench Aneesh Kumar K.V
2007-10-24 16:47 ` [PATCH] ext4: Enable delalloc and mballoc by default Aneesh Kumar K.V
2007-10-24 16:47 ` [PATCH] ext4: Show mballoc and delalloc options Aneesh Kumar K.V
2007-10-24 16:47 ` [PATCH] ext4: Fix ext4_show_options to show the correct mount options Aneesh Kumar K.V
2007-10-24 17:55 ` Eric Sandeen
2007-10-24 18:18 ` Aneesh Kumar K.V
2007-10-24 18:25 ` Eric Sandeen [this message]
2007-10-24 17:24 ` [PATCH] ext4: Show mballoc and delalloc options Eric Sandeen
2007-10-24 17:22 ` [PATCH] ext4: Enable delalloc and mballoc by default Eric Sandeen
2007-10-24 17:30 ` Aneesh Kumar K.V
2007-10-24 19:15 ` Mingming Cao
2007-10-24 21:06 ` Andreas Dilger
2007-10-24 21:15 ` Eric Sandeen
2007-10-24 22:59 ` Andreas Dilger
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=471F8E0B.7070202@redhat.com \
--to=sandeen@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.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 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.