From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: ext4 > 16T woes
Date: Fri, 25 May 2012 16:01:55 -0500 [thread overview]
Message-ID: <4FBFF343.9000706@redhat.com> (raw)
In-Reply-To: <4FBD3102.6050001@redhat.com>
On 5/23/12 1:48 PM, Eric Sandeen wrote:
> I'll try to look into this but just wanted to put it out there.
>
> After creating a 32T fs and filling it with 1T preallocated files,
> I get quite a lot of corruption; this wasn't really the test
> I wanted to do, I wanted to then remove a file with mostly
> high blocks, run fsstress, and test recovery :(
FWIW I tracked this down to the rbtree bitmap backend and sent
a patch,
[PATCH] libext2fs: Fix rbtree backend for extent lengths greater than 2^32
-Eric
> # uname -r
> 3.4.0-rc4+
> # truncate --size 32t imagefile2
> # mkfs.ext4 -F imagefile2
> mke2fs 1.42.3 (14-May-2012)
> ...
> # mount -o loop imagefile2 /mnt/scratch
> # for I in `seq 1 32`; do fallocate -l 1t /mnt/scratch/1tfile$I; done
> # umount /mnt/scratch
> # time e2fsck -fn imagefile2
> e2fsck 1.42.3 (14-May-2012)
> <many many many lines snipped>
> Free blocks count wrong for group #131072 (0, counted=32768).
> Fix? no
>
> Free blocks count wrong for group #131073 (0, counted=32768).
> Fix? no
>
> Free blocks count wrong for group #131074 (0, counted=4164).
> Fix? no
>
> Free blocks count wrong (3, counted=4294967299).
> Fix? no
>
>
> imagefile2: ********** WARNING: Filesystem still has errors **********
>
> imagefile2: 43/536870912 files (0.0% non-contiguous), 8589934589/8589934592 blocks
>
> real 27m40.133s
> user 27m12.886s
> sys 0m6.238s
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-05-25 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 18:48 ext4 > 16T woes Eric Sandeen
2012-05-23 19:33 ` Andreas Dilger
2012-05-23 19:48 ` Eric Sandeen
2012-05-25 21:01 ` Eric Sandeen [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=4FBFF343.9000706@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/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.