From: Jan Kara <jack@suse.cz>
To: Mingming <cmm@us.ibm.com>
Cc: Eric Sandeen <sandeen@redhat.com>, Jiri Kosina <jkosina@suse.cz>,
Pavol Cvengros <pavol.cvengros@primeinteractive.net>,
linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org
Subject: Re: ext4+quota+nfs issue
Date: Thu, 10 Sep 2009 14:40:56 +0200 [thread overview]
Message-ID: <20090910124056.GI607@duck.suse.cz> (raw)
In-Reply-To: <1252531929.19097.174.camel@mingming-laptop>
On Wed 09-09-09 14:32:09, Mingming wrote:
> On Wed, 2009-09-09 at 10:02 -0500, Eric Sandeen wrote:
> > Jiri Kosina wrote:
> > > [ adding relevant CCs ]
> > >
> > > On Wed, 9 Sep 2009, Pavol Cvengros wrote:
> > >
> > >> Hi,
> > >>
> > >> can somebody who is aware of ext4 and quota have a look on this one?
> > >>
> >
> > This was also just reported at:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=521914
> >
>
> Checked the bugzilla, it seems the fs enabled quota, but no user quota
> limit is specified. Is this the case with the ext4 quota+ nfs issue too?
>
> If no user quota is specified, then IS_NOQUOTA() should avoid doing
> quota reservation/claim at all. Not sure what is missing... I will check
> if I could reproduce this on local filesystem...
Mingming, IS_NOQUOTA() check is true only for quota-files. For all other
files it is false since we have to know how much space each user uses even
if it does not have a quota limit set (for the case that someone sets the
limit in future).
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2009-09-10 12:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AA5E5F3.30309@primeinteractive.net>
[not found] ` <4AA72C14.1020005@primeinteractive.net>
2009-09-09 9:42 ` ext4+quota+nfs issue Jiri Kosina
2009-09-09 14:46 ` Jan Kara
2009-09-09 17:19 ` Pavol Cvengros
2009-09-09 15:02 ` Eric Sandeen
2009-09-09 17:45 ` Justin Maggard
2009-09-09 19:02 ` Pavol Cvengros
2009-09-11 14:33 ` Pavol Cvengros
2009-09-14 17:50 ` Jan Kara
2009-09-14 18:52 ` Aneesh Kumar K.V
2009-09-16 6:35 ` Pavol Cvengros
2009-09-21 16:28 ` Mingming
2009-09-09 21:32 ` Mingming
2009-09-10 3:21 ` Pavol Cvengros
2009-09-10 12:40 ` Jan Kara [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=20090910124056.GI607@duck.suse.cz \
--to=jack@suse.cz \
--cc=cmm@us.ibm.com \
--cc=jkosina@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavol.cvengros@primeinteractive.net \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).