From: Dave Chinner <david@fromorbit.com>
To: "Weber, Charles (NIH/NIA/IRP) [C]" <weberc@grc.nia.nih.gov>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: weird quota issue
Date: Tue, 23 Dec 2014 11:32:37 +1100 [thread overview]
Message-ID: <20141223003237.GA4521@dastard> (raw)
In-Reply-To: <2F3F57BB-59EA-4FF9-9254-6A598DE7AC46@grc.nia.nih.gov>
On Mon, Dec 22, 2014 at 05:46:42PM -0500, Weber, Charles (NIH/NIA/IRP) [C] wrote:
> I wonder if it is a thin-provision issue? ~40TB allocated by the SAN but setup to not really allocate space until it is claimed by the OS.
>
> xfs_db -c "sb 0" -c p /dev/dm-7
>
....
> versionnum = 0xb5e4
So the quota bit is set (0x40) hence quotas will attempt to be
enabled.
> uquotino = 131
> gquotino = 0
> qflags = 0
But we have no quota enabled but a user quota inode allocated.
the quota flags would have been written to zero by the initial
failure, so this implies that reading the user quota inode failed.
Output of 'xfs_db -c "inode 131" -c p /dev/dm-7', please?
-Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-12-23 0:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 21:26 weird quota issue Weber, Charles (NIH/NIA/IRP) [E]
2014-12-22 16:34 ` Charles Weber
2014-12-22 20:48 ` Dave Chinner
2014-12-22 22:13 ` Weber, Charles (NIH/NIA/IRP) [C]
2014-12-22 22:35 ` Dave Chinner
2014-12-22 22:46 ` Weber, Charles (NIH/NIA/IRP) [C]
2014-12-23 0:32 ` Dave Chinner [this message]
2014-12-23 2:12 ` Weber, Charles (NIH/NIA/IRP) [E]
2014-12-23 2:42 ` Dave Chinner
2014-12-23 7:19 ` Arkadiusz Miśkiewicz
2014-12-23 20:35 ` Dave Chinner
2014-12-23 16:31 ` Weber, Charles (NIH/NIA/IRP) [C]
2014-12-23 18:48 ` Weber, Charles (NIH/NIA/IRP) [C]
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=20141223003237.GA4521@dastard \
--to=david@fromorbit.com \
--cc=weberc@grc.nia.nih.gov \
--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