From: gus3 <musicman529@yahoo.com>
To: Karel Zak <kzak@redhat.com>, Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@lst.de>,
Jasper Bryant-Greene <jasper@amiton.co.nz>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
util-linux-ng@vger.kernel.org
Subject: Re: XFS noikeep remount in 2.6.27-rc1-next-20080730
Date: Tue, 5 Aug 2008 21:33:52 -0700 (PDT) [thread overview]
Message-ID: <510965.21937.qm@web34502.mail.mud.yahoo.com> (raw)
In-Reply-To: <20080805233956.GI21635@disturbed>
--- On Tue, 8/5/08, Dave Chinner <david@fromorbit.com> wrote:
> So what is the correct behaviour? Should the filesystem
> *silently
> ignore* unchangable options in the remount command, or
> should it
> fail the remount and warn the user that certain options are
> not
> allowed in remount?
How about a middle ground: ignore, but not silently? Report an error, or send it to the syslog, or both, but ultimately ignore unchangeable options, change what can be changed, and give the user/admin as much as possible.
This can be particularly pertinent for XFS root. If it's mounted RO at first, it may (will?) need to become RW at some later point. Failing the remount could result in a system that requires a rescue CD (or lots of headaches for remote administration).
next prev parent reply other threads:[~2008-08-06 4:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 1:19 XFS noikeep remount in 2.6.27-rc1-next-20080730 Jasper Bryant-Greene
2008-08-01 7:30 ` Dave Chinner
2008-08-01 19:31 ` Christoph Hellwig
2008-08-05 11:03 ` Karel Zak
2008-08-05 23:39 ` Dave Chinner
2008-08-05 23:44 ` Jasper Bryant-Greene
2008-08-06 0:53 ` Dave Chinner
2008-08-06 4:33 ` gus3 [this message]
2008-08-06 4:36 ` Jasper Bryant-Greene
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=510965.21937.qm@web34502.mail.mud.yahoo.com \
--to=musicman529@yahoo.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=jasper@amiton.co.nz \
--cc=kzak@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=util-linux-ng@vger.kernel.org \
--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