From: Ben Myers <bpm@sgi.com>
To: "Weber, Charles (NIH/NIA/IRP) [C]" <WeberC@grc.nia.nih.gov>
Cc: xfs@oss.sgi.com
Subject: Re: prjquota not updating used blocks
Date: Fri, 9 Aug 2013 10:19:57 -0500 [thread overview]
Message-ID: <20130809151957.GZ3111@sgi.com> (raw)
In-Reply-To: <6D3CECD5-FBBF-4946-A0D0-5B0C71E772DD@grc.nia.nih.gov>
Hi Charles,
On Fri, Aug 09, 2013 at 10:14:21AM -0400, Weber, Charles (NIH/NIA/IRP) [C] wrote:
> CentOS 6.4
> Linux niairpfs1.irp.nia.nih.gov 2.6.32-358.6.2.el6.x86_64 #1 SMP Thu May 16 20:59:36 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
> xfsprogs-3.1.1-10.el6_4.1.x86_64
> xfsdump-3.0.4-3.el6.x86_64
>
> mount
> /dev/mapper/shared1_vg-niairp_lv on /share/niairp type xfs (rw,delaylog,inode64,nobarrier,logbsize=256k,uquota,prjquota)
>
> this is a 63T filesystem
> xfs_quota report
> Project quota on /share/niairp (/dev/mapper/shared1_vg-niairp_lv)
> Project ID Used Soft Hard Warn/Grace
> ---------- ---------------------------------
> lbnnas 0 0 1T 00 [------]
> lbnnccu 0 0 4.4T 00 [------]
> tgb 1.3T 0 2T 00 [------]
> apps 106.4G 0 150G 00 [------]
> ncts 205.7G 0 250G 00 [------]
> lg 1.4T 0 10T 00 [------]
>
> Since initializing a project quota, there is no change in used blocks. When I initialize the block count is correct. If I re-initialize, the used block count is updated properly.
>
> I copied 2T last night into the folder referenced by the lg project quota and there is no change in used blocks today.
> What have I missed?
An initial guess is you did not set up the project in xfs_quota using the
'project -s' xfs_quota command.
'project -c' output should look like this:
xfs_quota> project -c testproject
Checking project testproject (path /mnt/test/testa)...
Checking project testproject (path /mnt/test/testb)...
Processed 2 (/etc/projects and cmdline) paths for project testproject with recursion depth infinite (-1).
But if you don't set up a project you might see something like this:
xfs_quota> project -c testproject
Checking project testproject (path /mnt/test/testa)...
/mnt/test/testa - project identifier is not set (inode=0, tree=33)
/mnt/test/testa - project inheritance flag is not set
/mnt/test/testa/file - project identifier is not set (inode=0, tree=33)
/mnt/test/testa/file - project inheritance flag is not set
Checking project testproject (path /mnt/test/testb)...
/mnt/test/testb - project identifier is not set (inode=0, tree=33)
/mnt/test/testb - project inheritance flag is not set
Processed 2 (/etc/projects and cmdline) paths for project testproject with recursion depth infinite (-1).
And you'd have similar symptoms. You can also check which project the files
you created are in by using the xfs_io 'lsproj' command. There is also a
'chproj' command if find that your existing files aren't in the project and
need to add them in.
Regards,
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-08-09 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 14:14 prjquota not updating used blocks Weber, Charles (NIH/NIA/IRP) [C]
2013-08-09 15:19 ` Ben Myers [this message]
2013-08-09 16:29 ` Weber, Charles (NIH/NIA/IRP) [C]
2013-08-09 17:17 ` Ben Myers
2013-08-09 18:27 ` 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=20130809151957.GZ3111@sgi.com \
--to=bpm@sgi.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