All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Jasper Bryant-Greene <jasper@amiton.co.nz>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com, hch@lst.de
Subject: Re: XFS noikeep remount in 2.6.27-rc1-next-20080730
Date: Fri, 1 Aug 2008 17:30:33 +1000	[thread overview]
Message-ID: <20080801073033.GF6201@disturbed> (raw)
In-Reply-To: <1217553598.3860.16.camel@luna.unix.geek.nz>

[cc'd xfs@oss.sgi.com]

On Fri, Aug 01, 2008 at 01:19:58PM +1200, Jasper Bryant-Greene wrote:
> I mount a bunch of XFS filesystems with "noikeep,attr2,noatime", and a
> couple also with "ro".
> 
> Sometimes I want to remount one of the "ro" ones "rw", to make changes.
> This doesn't work anymore in 2.6.27-rc1-next-20080730. The last kernel I
> tried which it worked in was 2.6.26 release.
> 
> luna ~ # mount -o remount,rw /usr
> mount: /usr not mounted already, or bad option
> 
> luna ~ # dmesg | tail -n 1
> [18702.291344] XFS: mount option "noikeep" not supported for remount
> 
> Is this intended behaviour?

Side effect of this commit:

http://oss.sgi.com/cgi-bin/gitweb.cgi?p=xfs/xfs-2.6.git;a=commit;h=0327f9d799ebb96f67c80dd732b1fdb09527365e

Christoph?

FWIW, noikeep is the default, so you don't need to specify it.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2008-08-01  7:29 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 [this message]
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
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=20080801073033.GF6201@disturbed \
    --to=david@fromorbit.com \
    --cc=hch@lst.de \
    --cc=jasper@amiton.co.nz \
    --cc=linux-kernel@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 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.