From: Eric Sandeen <sandeen@sandeen.net>
To: Chris Walker <christopher.walker@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: kernel BUG with xfs_quota
Date: Thu, 09 Jul 2009 23:00:30 -0500 [thread overview]
Message-ID: <4A56BCDE.2010609@sandeen.net> (raw)
In-Reply-To: <554e24be0907091624s2dd439b2vfd7062f6b866c7f@mail.gmail.com>
Chris Walker wrote:
> Hello,
>
> I ran an xfs_quota command earlier (xfs_quota -x -c 'limit -g
> bsoft=2048g bhard=2148g hepl' /seltzer_lab), which triggered a kernel
> BUG:
>
> Assertion failed: dst->d_btimer != 0, file:
> fs/xfs/quota/xfs_qm_syscalls.c, line: 927
Well, you hit this:
#ifdef DEBUG
if (((XFS_IS_UQUOTA_ENFORCED(mp) && dst->d_flags ==
XFS_USER_QUOTA) ||
(XFS_IS_OQUOTA_ENFORCED(mp) &&
(dst->d_flags & (XFS_PROJ_QUOTA |
XFS_GROUP_QUOTA)))) &&
dst->d_id != 0) {
if (((int) dst->d_bcount >= (int) dst->d_blk_softlimit) &&
(dst->d_blk_softlimit > 0)) {
ASSERT(dst->d_btimer != 0);
}
...
which first raises the question, why are you running with
CONFIG_XFS_DEBUG? :)
I'm no quota guru, but this is something like...
If quota is enabled and the block count is over a non-0 soft limit, then
assert that the timer is non-0 (the timer being how much time is left
before service is refused.
It also got all those values off the disk just prior to the ASSERT.
... and I'm not sure what the problem may be. But you hit an internal
debugging assert which is only on with CONFIG_XFS_DEBUG, you may get
away with just running without that for now :)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-07-10 3:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 23:24 kernel BUG with xfs_quota Chris Walker
2009-07-10 4:00 ` Eric Sandeen [this message]
2009-07-10 14:57 ` Chris Walker
2009-07-10 14:59 ` Eric Sandeen
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=4A56BCDE.2010609@sandeen.net \
--to=sandeen@sandeen.net \
--cc=christopher.walker@gmail.com \
--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