public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: weber@zbfmail.de, Xfs <xfs@oss.sgi.com>
Subject: Re: gentoo linux, kernel 3.10.31 mount options bug?
Date: Sun, 23 Feb 2014 10:07:47 -0600	[thread overview]
Message-ID: <530A1CD3.8070204@sandeen.net> (raw)
In-Reply-To: <9963a76fbd006355c9ffd79f341c9971@zbfmail.de>

On 2/23/14, 3:37 AM, Marko Weber|8000 wrote:
> 
> 
> hello list,
> 
> i have a question about mount options.
> 
> at first my fstab:
> 
> /dev/md0                /boot           xfs             noauto,noatime  1 2
> /dev/md2                /               xfs             noatime,nodiratime,nobarrier,largeio,discard,logbsize=256k,noikeep      0 1

I guess I won't ask why you decided to tweak all those knobs...

<snip>

> (YES!, normally i use Label or UUID..... but this is only a test machine.....)
> 
> 
> AFTER reboot "mount" shows this:
> 
> rootfs on / type rootfs (rw)
> /dev/root on / type xfs (rw,noatime,nodiratime,attr2,nobarrier,inode64,noquota)

<snip>

default mount options

> 
> on /dev/root "discrad" and some other are not shown
> 
> 
> when i do a "mount -o remount /"
> 
> "mount" shows this:
> 
> 
> rootfs on / type rootfs (rw)
> /dev/root on / type xfs (rw,noatime,nodiratime,nobarrier,largeio,discard,logbsize=256k,noikeep)
> /dev/md1 on /tmp type xfs (rw,noexec,noatime,nodiratime,nobarrier,largeio,discard,logbsize=256k,noikeep)

tweaked options.

<snip>

> 
> now,all options from /etc/fstab are listed.
> Is this XFS related?

Not really.  Only some xfs options are remountable, so unless you originally mounted with, say, "largeio" the option won't be in effect.  Mount -o remount won't enable it.  So if you really want all those options enabled on your root fs, you'll need to have them in your initrd/initramfs so that the original mount of the root fs at boot time includes them.

Also, mount may be looking at /etc/mtab rather than /proc/mounts.  /proc/mounts contains the true state of the fileystem w.r.t. mount options.  /etc/mtab is managed by mount, and knows nothing about what the filesystem actually did:

[root@sandeen ~]# mount -o remount,notanoption /home

[root@sandeen ~]# mount | grep home
/dev/md2 on /home type xfs (rw,notanoption)

[root@sandeen ~]# grep home /proc/mounts
/dev/md2 /home xfs rw,seclabel,relatime,attr2,delaylog,noquota 0 0

-Eric


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-02-23 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23  9:37 gentoo linux, kernel 3.10.31 mount options bug? Marko Weber|8000
2014-02-23 16:07 ` Eric Sandeen [this message]
2014-02-23 22:10 ` Stan Hoeppner
2014-02-25  8:10   ` Marko Weber|8000

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=530A1CD3.8070204@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=weber@zbfmail.de \
    --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