From: supersud501 <supersud501@yahoo.de>
To: Theodore Tso <tytso@MIT.EDU>
Cc: Eric Sandeen <sandeen@redhat.com>, linux-ext4@vger.kernel.org
Subject: Re: e2fsck (git) on ext4: unsupported feature(s): huge_file
Date: Wed, 09 Apr 2008 20:12:52 +0200 [thread overview]
Message-ID: <47FD0724.4060307@yahoo.de> (raw)
In-Reply-To: <20080409161117.GB26924@mit.edu>
Theodore Tso wrote:
> That patch which I just sent out passes the regression test suite, but
> it hasn't been extensively tested for actual *huge* files.
> (Specifically, files with the EXT4_HUGE_FILE_FL because they are
> larger than 2TB and so i_blocks had to be specified in units of
> filesystem blocksize, instead of units of 512 bytes.)
>
> If you could apply the patch I just sent out and then run "e2fsck -nf
> /dev/sdXXX" and let me know you get, that would be much appreciated.
>
with this patch (and huge_files enabled) i get much more errors
(>1000++) of the following type:
inode x, i_blocks is y, should be y/8
inoda x+1, iblocks is z, should be z/8
.....
for example:
Inode 32538663, i_blocks is 8, should be 1. Fix? no
Inode 32538664, i_blocks is 8, should be 1. Fix? no
Inode 32538665, i_blocks is 8, should be 1. Fix? no
Inode 32538666, i_blocks is 40, should be 5. Fix? no
Inode 32538667, i_blocks is 32, should be 4. Fix? no
Inode 32538668, i_blocks is 8, should be 1. Fix? no
Inode 32538669, i_blocks is 8, should be 1. Fix? no
Inode 32538670, i_blocks is 8, should be 1. Fix? no
....
Inode 32587785, i_blocks is 17320, should be 2165. Fix? no
Inode 32587786, i_blocks is 16936, should be 2117. Fix? no
Inode 32587787, i_blocks is 120, should be 15. Fix? no
<------------ there are also gaps, not always x+1
Inode 32604181, i_blocks is 8, should be 1. Fix? no
Inode 32604161, i_blocks is 18624, should be 2328. Fix? no
Inode 32604162, i_blocks is 19400, should be 2425. Fix? no
Inode 32604163, i_blocks is 18800, should be 2350. Fix? no
Inode 32604164, i_blocks is 16488, should be 2061. Fix? no
Inode 32604165, i_blocks is 17832, should be 2229. Fix? no
Inode 32604166, i_blocks is 17880, should be 2235. Fix? no
Inode 32604167, i_blocks is 20560, should be 2570. Fix? no
Inode 32604168, i_blocks is 20480, should be 2560. Fix? no
Inode 32604169, i_blocks is 18224, should be 2278. Fix? no
not good?
next prev parent reply other threads:[~2008-04-09 18:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 17:58 e2fsck (git) on ext4: unsupported feature(s): huge_file supersud501
2008-04-08 18:36 ` Eric Sandeen
2008-04-08 19:45 ` supersud501
2008-04-08 21:00 ` Theodore Tso
2008-04-09 9:15 ` supersud501
2008-04-09 16:11 ` Theodore Tso
2008-04-09 17:53 ` supersud501
2008-04-09 18:59 ` Theodore Tso
2008-04-09 19:23 ` supersud501
2008-04-09 17:56 ` supersud501
2008-04-09 18:12 ` supersud501 [this message]
2008-04-09 19:06 ` Theodore Tso
2008-04-09 19:19 ` supersud501
2008-04-09 21:08 ` Theodore Tso
2008-04-11 13:04 ` Theodore Tso
2008-04-11 13:38 ` supersud501
2008-04-09 15:50 ` [E2FSPROGS, PATCH] Add support for the HUGE_FILE feature Theodore Ts'o
2008-04-09 12:54 ` e2fsck (git) on ext4: unsupported feature(s): huge_file Eric Sandeen
2008-04-09 14:45 ` Calvin Walton
2008-04-09 14:52 ` supersud501
2008-04-09 16:09 ` Eric Sandeen
2008-04-08 18:37 ` Eric Sandeen
2008-04-08 22:40 ` Christian Kujau
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=47FD0724.4060307@yahoo.de \
--to=supersud501@yahoo.de \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@MIT.EDU \
/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