All of lore.kernel.org
 help / color / mirror / Atom feed
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 12:17:50 -0500	[thread overview]
Message-ID: <20130809171750.GV1681@sgi.com> (raw)
In-Reply-To: <C33DFB5C-9524-4D7D-8F9A-8E17088CA20E@grc.nia.nih.gov>

Hey Charles,

On Fri, Aug 09, 2013 at 12:29:20PM -0400, Weber, Charles (NIH/NIA/IRP) [C] wrote:
> When I referred to initialize I meant  running xfs_quota -x project -s name

Hmm.  What if you used 'xfs_quota -x project -s -p /path/to/new/dirs name'?

> When I run xfs_quota -x 'project -c lg'
>
> I do get warnings about project identifier and inheritance but only for the
> new directories that I created and copied the large data sets into. I don't
> get those warning about the earlier files and folders for a given project.

Those warnings refer to not having a project id set in the inode core, and
whether a directory will set it's project id into the inode cores of whatever
you create inside.  Without that project id set in the new files you create,
the quota subsystem won't know which project quota to reserve blocks
against.  That's why your block usage wasn't changing.

> When I run the project -s again it does update the block usage.

Maybe the first try failed to find the new directory?  I'm not sure.

> But I would think the block usage should update automatically.

Could you cut an paste the procedure to you used to create the new directories?

Thanks,
	Ben

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-08-09 17:17 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
2013-08-09 16:29   ` Weber, Charles (NIH/NIA/IRP) [C]
2013-08-09 17:17     ` Ben Myers [this message]
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=20130809171750.GV1681@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 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.