public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Marko Weber | 8000 <weber@zbfmail.de>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: an mount option question and dunno if right here...
Date: Wed, 16 Mar 2016 14:03:28 +0100	[thread overview]
Message-ID: <ebcb0a57f224c5a9be0d2d2777bca581@zbfmail.de> (raw)
In-Reply-To: <56E1A8B1.2080800@sandeen.net>



Am 2016-03-10 18:02, schrieb Eric Sandeen:
> On 3/9/16 4:35 AM, Marko Weber | 8000 wrote:
>> 
>> 
>> hello list,
>> 
>> my drives are all xfs formatted.
>> in fstab i set:
>> 
>>                  lazytime,logbsize=256k,logbufs=8
>> 
>> 
>> when i call "mount" on console i get:
>> 
>>                  
>> rw,relatime,lazytime,attr2,inode64,logbufs=8,logbsize=256k,sunit=1024,swidth=3072,noquota
>> 
>> 
>> Why is relatime listed? Or is lazytime override this setting?
>> Even when i set "norelatime" in /etc/fstab i get "relatime" listed on 
>> 'mount'
>> 
>> Or am i wrong here with this question? is this not xfs related?
>> anyway, for any hints or suggestions i am thankful
> 
> lazytime is not a valid xfs mount option:
> 
> [root ~]# mount -o lazytime /dev/sdb1 /mnt/test
> mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
> missing codepage or helper program, or other error
> In some cases useful info is found in syslog - try
> dmesg | tail or so
> 
> [root ~]# dmesg | tail -n 1
> [645779.811802] XFS (sdb1): unknown mount option [lazytime].
> 
> I'm guessing this is your root fs? xfs today will silently ignore
> unknown mount options on remount (patches to fix that are upstream),
> and the root fs may get remounted w/ fstab options.  So presumably
> that's how you got lazytime into the mount output, especially if
> it's looking at /etc/mtab. Look in /proc/mounts; I doubt you'll
> see "lazytime" for this filesystem:
> 
> [root ~]# mount /dev/sdb1 /mnt/test
> [root ~]# mount -o remount,lazytime /mnt/test
> 
> [root ~]# grep sdb1 /etc/mtab /proc/mounts
> /etc/mtab:/dev/sdb1 /mnt/test xfs rw,lazytime 0 0
> /proc/mounts:/dev/sdb1 /mnt/test xfs
> rw,seclabel,relatime,attr2,inode64,noquota 0 0

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






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

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

  reply	other threads:[~2016-03-16 13:03 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 [this message]
2016-03-16 13:48     ` Eric Sandeen
2016-03-16 19:34       ` Dave Chinner

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