From: Justin Maggard <jmaggard10@gmail.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: 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: Wed, 9 Sep 2009 10:45:06 -0700 [thread overview]
Message-ID: <150c16850909091045h1962fd67n77c265c9b99c5f44@mail.gmail.com> (raw)
In-Reply-To: <4AA7C38E.8020306@redhat.com>
On Wed, Sep 9, 2009 at 8:02 AM, Eric Sandeen<sandeen@redhat.com> wrote:
>> 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
>
> -Eric
>
I've seen exactly the same thing myself as well, but on local I/O.
The only difference I was able to find between filesystems I saw this
on, versus filesystems that I didn't see this on, was how it was
created. The filesystems without this issue were made using
mkfs.ext4, and the ones that _did_ have the issue were created with
mkfs.ext3, and then mounted -t ext4. Pavol, can you check your
filesystem features from "dumpe2fs -h [your_device]"?
-Justin
next prev parent reply other threads:[~2009-09-09 17:45 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 [this message]
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
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=150c16850909091045h1962fd67n77c265c9b99c5f44@mail.gmail.com \
--to=jmaggard10@gmail.com \
--cc=jack@suse.cz \
--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).