public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: 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 13:03:57 +0200	[thread overview]
Message-ID: <20080805110357.GL21873@nb.net.home> (raw)
In-Reply-To: <20080801193133.GA838@lst.de>

On Fri, Aug 01, 2008 at 09:31:33PM +0200, Christoph Hellwig wrote:
> I'ts most likely a fallout, but I wonder why.  To get this behaviour
> moutn would have to add all the options it finds in /proc/self/mounts
> to the command line.

 mount(8) does not read and use /proc/self/mounts at all.

    Karel


 Man mount:

 remount

     Attempt  to remount an already-mounted file system.  This is commonly used
     to change the mount flags for a file system, especially to make a readonly
     file system writeable. It does not change device or mount point.

     The  remount  functionality follows the standard way how the mount command
     works with options from fstab. It means the  mount  command  doesn’t  read
     fstab (or mtab) only when a device and dir are fully specified.

     mount -o remount,rw /dev/foo /dir

     After  this  call  all  old mount options are replaced and arbitrary stuff
     from fstab is ignored, except the loop= option which is internally  gener-
     ated and maintained by the mount command.

     mount -o remount,rw  /dir

     After  this call mount reads fstab (or mtab) and merges these options with
     options from command line ( -o ).


-- 
 Karel Zak  <kzak@redhat.com>

  reply	other threads:[~2008-08-05 11:04 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 [this message]
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=20080805110357.GL21873@nb.net.home \
    --to=kzak@redhat.com \
    --cc=hch@lst.de \
    --cc=jasper@amiton.co.nz \
    --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