From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 09/10] Implement quota support for disabling SPARSE feature
Date: Wed, 29 Jul 2009 11:32:51 -0700 [thread overview]
Message-ID: <20090729183251.GC5849@mail.oracle.com> (raw)
In-Reply-To: <20090729101245.GE19209@duck.suse.cz>
On Wed, Jul 29, 2009 at 12:12:45PM +0200, Jan Kara wrote:
> On Tue 28-07-09 18:39:45, Joel Becker wrote:
> > I read this as we adjust the quota but don't enforce it. That is, if
> > filling a hole will make a user over quota, we allow that to happen.
> > Right?
> Yes, that's what I've decided makes the most sense. It's in the spirit
> of "superuser ignores quota limits". Alternatively, we could issue a
> warning or even fail the conversion when some user would go over quota
> limit but I don't really see the use case.
I agree, the superuser is asking for sparse to be removed, and
they have no quota. Upon remount, the regular user obviously can't
create anything until they get below quota. So this is the right
behavior.
Joel
--
"Sometimes one pays most for the things one gets for nothing."
- Albert Einstein
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2009-07-29 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 10:18 [Ocfs2-devel] [PATCH 9-10/10] Quota support for disabling sparse feature Jan Kara
2009-07-28 10:18 ` [Ocfs2-devel] [PATCH 09/10] Implement quota support for disabling SPARSE feature Jan Kara
2009-07-29 1:39 ` Joel Becker
2009-07-29 10:12 ` Jan Kara
2009-07-29 18:32 ` Joel Becker [this message]
2009-07-28 10:18 ` [Ocfs2-devel] [PATCH 10/10] Fix tunefs space check when " Jan Kara
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=20090729183251.GC5849@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=ocfs2-devel@oss.oracle.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.