From: Pavol Cvengros <pavol.cvengros@primeinteractive.net>
To: Justin Maggard <jmaggard10@gmail.com>
Cc: Eric Sandeen <sandeen@redhat.com>, Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org
Subject: Re: ext4+quota+nfs issue
Date: Fri, 11 Sep 2009 16:33:48 +0200 [thread overview]
Message-ID: <4AAA5FCC.2010707@primeinteractive.net> (raw)
In-Reply-To: <4AA7FBD7.9080406@primeinteractive.net>
Hi,
did this dump helped ?
Should I try something?
P.
On 9/9/2009 9:02 PM, Pavol Cvengros wrote:
> On 9/9/2009 7:45 PM, Justin Maggard wrote:
>> 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
>> --
>
> here is the dump....
>
> host_stor0 ~ # dumpe2fs -h /dev/sdb1
> dumpe2fs 1.41.9 (22-Aug-2009)
> Filesystem volume name: <none>
> Last mounted on: <not available>
> Filesystem UUID: f8aef49b-1903-4e25-9a7b-a3f5557107fb
> Filesystem magic number: 0xEF53
> Filesystem revision #: 1 (dynamic)
> Filesystem features: has_journal ext_attr resize_inode dir_index
> filetype needs_recovery extent flex_bg sparse_super large_file
> huge_file uninit_bg dir_nlink extra_isize
> Filesystem flags: signed_directory_hash
> Default mount options: (none)
> Filesystem state: clean
> Errors behavior: Continue
> Filesystem OS type: Linux
> Inode count: 305176576
> Block count: 1220689911
> Reserved block count: 12206899
> Free blocks: 977820919
> Free inodes: 250981592
> First block: 0
> Block size: 4096
> Fragment size: 4096
> Reserved GDT blocks: 732
> Blocks per group: 32768
> Fragments per group: 32768
> Inodes per group: 8192
> Inode blocks per group: 512
> Flex block group size: 16
> Filesystem created: Tue Jun 30 20:04:20 2009
> Last mount time: Tue Aug 18 12:21:18 2009
> Last write time: Tue Aug 18 12:21:18 2009
> Mount count: 10
> Maximum mount count: -1
> Last checked: Tue Jun 30 20:04:20 2009
> Check interval: 0 (<none>)
> Lifetime writes: 73 GB
> Reserved blocks uid: 0 (user root)
> Reserved blocks gid: 0 (group root)
> First inode: 11
> Inode size: 256
> Required extra isize: 28
> Desired extra isize: 28
> Journal inode: 8
> Default directory hash: half_md4
> Directory Hash Seed: 317c2fc4-9c86-42ca-a3c3-0d6c632dcb46
> Journal backup: inode blocks
> Journal size: 128M
>
> P.
next prev parent reply other threads:[~2009-09-11 14:33 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 [this message]
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=4AAA5FCC.2010707@primeinteractive.net \
--to=pavol.cvengros@primeinteractive.net \
--cc=jack@suse.cz \
--cc=jkosina@suse.cz \
--cc=jmaggard10@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).