From: Xavier Roche <roche+kml2@exalead.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.31 / 2.6.32-last: XFS will not mount after a crash when quotas are enabled (quota DB corrupted)
Date: Thu, 29 Oct 2009 17:09:05 +0100 [thread overview]
Message-ID: <4AE9BE21.8020102@exalead.com> (raw)
Hi folks,
We experience issues with XFS on Kernel >= 2.6.31 when quotas are
enabled. Some recent quotas additions might be the cause of the problems
encountered. (1)
Test case to reproduce the issue:
---------------------------------
- Have an XFS filesystem with quotas enabled for users
/etc/fstab entry:
/dev/sda6 /data xfs uqupta,gquota 0 0
- Have a kernel crash while the filesystem is dirty
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git &
sleep 10
echo b >/proc/sysrq-trigger
# we should dead here
On reboot, after the filesystem check, the filesystem will not mount
because the quota db is apparently corrupted:
XFS: dquot too small (104) in xlog_recover_do_dquot_trans.
The filesystem is however still fixable using:
mount -o noquota /data
umount /data
mount /data
(however this will rebuild the entire DB..)
The issue could not be reproduced on a 2.6.30
(1) http://xfs.org/index.php/XFS_Status_Updates
"The Linux 2.6.31 merge opened in the mid of the month and some big XFS
changes have been pushed: A removal of the quotaops infrastructure which
simplifies the quota implementation, the switch from XFS's own Posix ACL
implementation to the generic one shared by various other filesystems
which also supports in-memory caching of ACLs and another incremental
refactoring of the sync code"
reply other threads:[~2009-10-29 16:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4AE9BE21.8020102@exalead.com \
--to=roche+kml2@exalead.com \
--cc=linux-kernel@vger.kernel.org \
/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