From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com, weber@zbfmail.de
Subject: Re: an mount option question and dunno if right here...
Date: Thu, 17 Mar 2016 06:34:36 +1100 [thread overview]
Message-ID: <20160316193436.GF11812@dastard> (raw)
In-Reply-To: <56E9641D.7010203@sandeen.net>
On Wed, Mar 16, 2016 at 08:48:13AM -0500, Eric Sandeen wrote:
> On 3/16/16 8:03 AM, Marko Weber | 8000 wrote:
> >
>
> > Hi Eric,
> >
> >
> > my /etc/fstab entry:
> >
> > /dev/VolGroup01/wiso /raid5/wiso xfs norelatime,lazytime
> >
> >
> >
> > # mount:
> >
> >
> > /dev/mapper/VolGroup01-wiso on /raid5/wiso type xfs (rw,relatime,lazytime,attr2,inode64,logbufs=8,logbsize=256k,sunit=1024,swidth=3072,noquota)
> >
> >
> > cat /proc/mounts:
> >
> > /dev/mapper/VolGroup01-wiso /raid5/wiso xfs rw,lazytime,relatime,attr2,inode64,logbufs=8,logbsize=256k,sunit=1024,swidth=3072,noquota 0 0
> >
>
> Ok, I stand corrected, sorry; I forgot about this:
>
> commit 0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8
> Author: Theodore Ts'o <tytso@mit.edu>
> Date: Mon Feb 2 00:37:00 2015 -0500
>
> vfs: add support for a lazytime mount option
Don't for that lazytime isn't actually implemented by XFS, and we
can't intercept that flag at mount time because it's been added as a
VFS flag. So on everything but ext4 it does nothing, it conflicts
with other atime settings we do support, and we can't really do
anything about it...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2016-03-16 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 10:35 an mount option question and dunno if right here Marko Weber | 8000
2016-03-09 11:01 ` Carlos E. R.
2016-03-10 17:02 ` Eric Sandeen
2016-03-16 13:03 ` Marko Weber | 8000
2016-03-16 13:48 ` Eric Sandeen
2016-03-16 19:34 ` Dave Chinner [this message]
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=20160316193436.GF11812@dastard \
--to=david@fromorbit.com \
--cc=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 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.