From: Eric Sandeen <sandeen@sandeen.net>
To: cbay@excellency.fr, xfs@oss.sgi.com
Subject: Re: Forced quotacheck after unclean unmount since 3.11, bisected
Date: Tue, 22 Jul 2014 11:48:05 -0500 [thread overview]
Message-ID: <53CE95C5.8040702@sandeen.net> (raw)
In-Reply-To: <53CE6415.8080607@excellency.fr>
On 7/22/14, 8:16 AM, Cyril B. wrote:
> Hello,
>
> I've noticed that since Linux 3.11, quotacheck always happen after
> unclean unmounts. Is this expected? It didn't happen on previous
> Linux versions.
I can reproduce this, I'll take a look - thanks for bisecting!
-Eric
> A bisect shows that this commit is responsible:
> xfs: Remove incore use of XFS_OQUOTA_ENFD and XFS_OQUOTA_CHKD
> id: 83e782e1a1cc0159888e58e14dfc8f3289663338
>
> Relevant dmesg:
> [ 8.844063] XFS (md4): Mounting Filesystem
> [ 9.054023] XFS (md4): Starting recovery (logdev: internal)
> [ 9.331785] XFS (md4): Ending recovery (logdev: internal)
> [ 9.383856] XFS (md4): Quotacheck needed: Please wait.
> [ 48.427732] XFS (md4): Quotacheck: Done.
>
> More details:
> * vanilla kernel
> * on top of mdadm (RAID1)
> * xfsprogs 3.1.5
> * mount options: noatime,nosuid,nodev,grpquota,inode64
> * xfs_info:
> meta-data=/dev/md4 isize=256 agcount=4, agsize=119997280 blks
> = sectsz=512 attr=2
> data = bsize=4096 blocks=479989120, imaxpct=5
> = sunit=0 swidth=0 blks
> naming =version 2 bsize=4096 ascii-ci=0
> log =internal bsize=4096 blocks=234369, version=2
> = sectsz=512 sunit=0 blks, lazy-count=1
> realtime =none extsz=4096 blocks=0, rtextents=0
>
> Thanks,
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-07-22 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 13:16 Forced quotacheck after unclean unmount since 3.11, bisected Cyril B.
2014-07-22 16:48 ` Eric Sandeen [this message]
2014-07-22 17:10 ` [PATCH] xfs: avoid false quotacheck after unclean shutdown Eric Sandeen
2014-07-23 13:20 ` Brian Foster
2014-07-24 23:29 ` [PATCH V2] " Eric Sandeen
2014-07-28 15:02 ` Brian Foster
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=53CE95C5.8040702@sandeen.net \
--to=sandeen@sandeen.net \
--cc=cbay@excellency.fr \
--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.