From: Eric Sandeen <sandeen@sandeen.net>
To: Jan Kara <jack@suse.cz>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: no quota output if no usage?
Date: Fri, 28 Nov 2014 10:40:06 -0600 [thread overview]
Message-ID: <5478A566.2080500@sandeen.net> (raw)
In-Reply-To: <20141127093225.GB30152@quack.suse.cz>
On 11/27/14 3:32 AM, Jan Kara wrote:
> On Wed 26-11-14 18:28:32, Eric Sandeen wrote:
>> On 11/26/14 4:18 PM, Dave Chinner wrote:
>>
>>>> Or am I missing something ...
>>>
>>> Nope, I'm confusing different reporting command behaviour....
>>
>> Ok, so back to the original question: think it's cool to drop
>> the verbose requirement to find out limits when there is 0 usage?
> Just as a data point quota(1) command from quota-tools also doesn't
> report quota entries where no space & inode is accounted without -v option.
> I never thought it's particularly useful but apparently it's some heritage
> from the original implementation of quota in some Unix and so I decided to
> maintain compatibility...
Thanks - sounds like maybe the weight of history is behind this. Perhaps
it'll just be a documentation fix to clarify what happens when there's no
block or inode used.
-Eric
> Honza
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-11-28 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 19:26 no quota output if no usage? Eric Sandeen
2014-11-26 21:21 ` Dave Chinner
2014-11-26 21:26 ` Eric Sandeen
2014-11-26 22:18 ` Dave Chinner
2014-11-27 0:28 ` Eric Sandeen
2014-11-27 9:32 ` Jan Kara
2014-11-28 16:40 ` Eric Sandeen [this message]
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=5478A566.2080500@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jack@suse.cz \
--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