From: "Ladislav Durchánek" <durchanek@gmail.com>
To: xfs@oss.sgi.com
Subject: FW: Tree Quota error message suggestion
Date: Sat, 29 Jul 2006 17:55:46 +0200 [thread overview]
Message-ID: <018f01c6b327$74523980$0201a8c0@reykjavik> (raw)
I forgot, i'm using XFS on Linux 2.6.17 Gentoo.
Láïa
_____
From: Ladislav Durchánek [mailto:durchanek@gmail.com]
Sent: Saturday, July 29, 2006 5:54 PM
To: 'xfs@oss.sgi.com'
Subject: Tree Quota error message suggestion
Hi everybody,
First at all I have to say that XFS is great. Especially its built-in quota
support is really nice thing. I found tree quotas extremely useful for
hosting servers where uploaded files are created with other owner than
customer is.
But there is a one thing which could be done better I think: When I define
tree quota and user tries to exceed id, error message returned is "No space
left on device" which is not true - there is a plenty of space on device.
Only when quota is totally full, next message is "Disk quota exceeded". I
think it should be better if first message will be also "Disk quota
exceeded".
Cheers
Láïa Durchánek
[[HTML alternate version deleted]]
next reply other threads:[~2006-07-29 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-29 15:55 Ladislav Durchánek [this message]
2006-07-29 18:17 ` FW: Tree Quota error message suggestion Federico Sevilla III
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='018f01c6b327$74523980$0201a8c0@reykjavik' \
--to=durchanek@gmail.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