From: Timothy Shimmin <tes@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs-oss <xfs@oss.sgi.com>, xfs-dev <xfs-dev@sgi.com>
Subject: Re: REVIEW: 980021 - fix up noattr2 mount option
Date: Mon, 28 Apr 2008 10:39:57 +1000 [thread overview]
Message-ID: <48151CDD.3070203@sgi.com> (raw)
In-Reply-To: <20080426063551.GA7193@infradead.org>
Christoph Hellwig wrote:
> On Wed, Apr 23, 2008 at 03:29:33PM +1000, Timothy Shimmin wrote:
>> Hi there,
>>
>> Mounting noattr2 in xfs fails to achieve anything AFAICT -
>> and it certainly doesn't do anything useful.
>
> The patch looks correct in that it turns off attr2 when using the mount
> option now. But the real question is why do we even need this option at
> all?
Good question.
I guess I just feel with the problems we've had with attr2 so far,
I feel it would be good to have an easy way to to go back if needed
at this point (and the option is there though busted).
Ideally, there would be no attr1 and no option to go back required.
--Tim
next prev parent reply other threads:[~2008-04-28 0:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 5:29 REVIEW: 980021 - fix up noattr2 mount option Timothy Shimmin
2008-04-26 6:35 ` Christoph Hellwig
2008-04-28 0:39 ` Timothy Shimmin [this message]
2008-04-28 5:58 ` Christoph Hellwig
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=48151CDD.3070203@sgi.com \
--to=tes@sgi.com \
--cc=hch@infradead.org \
--cc=xfs-dev@sgi.com \
--cc=xfs@oss.sgi.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