public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Jasper Bryant-Greene <jasper@amiton.co.nz>
Cc: Karel Zak <kzak@redhat.com>, Christoph Hellwig <hch@lst.de>,
	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: Wed, 6 Aug 2008 10:53:54 +1000	[thread overview]
Message-ID: <20080806005354.GL21635@disturbed> (raw)
In-Reply-To: <1217979862.2887.39.camel@luna.unix.geek.nz>

On Wed, Aug 06, 2008 at 11:44:22AM +1200, Jasper Bryant-Greene wrote:
> On Wed, 2008-08-06 at 09:39 +1000, Dave Chinner wrote:
> > We're seeing the second case where mount is merging all the options in
> > /etc/fstab into the options passed into the remount command. How is
> > the filesystem expected to behave in these difference cases? The
> > first simply changes the ro/rw status, the second potentially
> > asks for the filesystem to change a bunch of other mount options
> > as well, which it may not be able to do.
> > 
> > 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?
> 
> (forgive me, I'm an XFS user, not an XFS developer, so this might be
> ignorant)
> 
> The filesystem presumably knows what options it was originally mounted
> with.
> 
> Thus if you take the difference of the set of options you were mounted
> with, and the set of options you are now being asked to remount with,
> you have the options which are being asked to change.

Sure. But that does not answer my question about what to do with
options that can't be changed. Options can come from more than just
/etc/fstab - they can come from the mount command line itself as
entered by the admin. What do we do if an option is specified that
we do not support in a remount?

The problem is the way mount combines command line options with
options in fstab. I'm not questioning what you did - I'm asking what
the expected behaviour is supposed to be so we can make it behave
the same way as all the other filesystems.

> If changing any of them is unsupported I would expect an error, but in
> this case the result of taking the above set difference would be merely
> replacing ro with rw, and thus the filesystem is presumably capable of
> doing the remount.

Use the full device/directory syntax for the remount command and it
will do just that. The command you issued was not a "pure" remount,rw,
it was silently changed by mount....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2008-08-06  0:54 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 [this message]
2008-08-06  4:33         ` gus3
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=20080806005354.GL21635@disturbed \
    --to=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