From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS Quota Check OOM
Date: Wed, 01 Sep 2010 01:56:31 +0200 [thread overview]
Message-ID: <4C7D96AF.3000006@profihost.ag> (raw)
In-Reply-To: <20100831232817.GM705@dastard>
quota report returns nothing... :-( except two newlines...
# xfs_quota -x -c "report -phnN" /
#
Stefan
Am 01.09.2010 01:28, schrieb Dave Chinner:
> On Tue, Aug 31, 2010 at 03:30:34PM +0200, Stefan Priebe - Profihost AG wrote:
>> Hi!
>>
>> After booting the System to a RAM Image with prjquota (the quota
>> check wents fine) and upgrading to xfsprogs 3.1.3.
>>
>> I'm getting this when trying to setup a project Quota:
>> xfs_quota -x -c "project -s 2" /
>> Setting up project 2 (path /serverbackup/abc)...
>> Processed 1 (/etc/projects and cmdline) paths for project 2 with
>> recursion depth infinite (-1).
>
> That's normal, I think. Adding project quota involves descending the
> directory heirachy specified and adding the project id to every file
> and directory. You can limit the recursion depth it runs to if you
> want to, but the default (infinite) is to walk the entire heirarchy.
>
> You can confirm by running a quota report and checking the output...
>
> Cheers,
>
> Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-08-31 23:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 12:14 XFS Quota Check OOM Stefan Priebe - Profihost AG
2010-08-30 17:11 ` Stefan Priebe - Profihost AG
2010-08-31 7:36 ` Stefan Priebe - Profihost AG
2010-08-31 8:44 ` Emmanuel Florac
2010-08-31 12:25 ` Stefan Priebe - Profihost AG
2010-08-31 12:43 ` Emmanuel Florac
2010-08-31 12:56 ` Stefan Priebe - Profihost AG
2010-08-31 13:20 ` Emmanuel Florac
2010-08-31 13:30 ` Stefan Priebe - Profihost AG
2010-08-31 23:28 ` Dave Chinner
2010-08-31 23:56 ` Stefan Priebe - Profihost AG [this message]
2010-09-01 10:24 ` Christoph Hellwig
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=4C7D96AF.3000006@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=david@fromorbit.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