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 21:19:56 +0200 [thread overview]
Message-ID: <47FD16DC.1090502@yahoo.de> (raw)
In-Reply-To: <20080409190634.GA9430@mit.edu>
Theodore Tso wrote:
> On Wed, Apr 09, 2008 at 08:12:52PM +0200, supersud501 wrote:
>> 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
>
> Can you send me the output of debugfs's "stat <32538663>", "stat
> <32538664>", etc? And also the output of dumpe2fs -h for the filesystem?
>
> - Ted
>
Inode: 32538663 Type: regular Mode: 0640 Flags: 0x80000
Generation: 1807877460
User: 1000 Group: 1000 Size: 3902
File ACL: 0 Directory ACL: 0
Links: 1 Blockcount: 8
Fragment: Address: 0 Number: 0 Size: 0
ctime: 0x47dead07 -- Mon Mar 17 18:40:23 2008
atime: 0x47dead07 -- Mon Mar 17 18:40:23 2008
mtime: 0x45a5e96b -- Thu Jan 11 08:38:19 2007
BLOCKS:
(0):75131957
TOTAL: 1
Inode: 32538664 Type: regular Mode: 0640 Flags: 0x80000
Generation: 1807877461
User: 1000 Group: 1000 Size: 2984
File ACL: 0 Directory ACL: 0
Links: 1 Blockcount: 8
Fragment: Address: 0 Number: 0 Size: 0
ctime: 0x47dead07 -- Mon Mar 17 18:40:23 2008
atime: 0x47dead07 -- Mon Mar 17 18:40:23 2008
mtime: 0x45a5e96b -- Thu Jan 11 08:38:19 2007
BLOCKS:
(0):75131958
TOTAL: 1
dumpe2fs:
dumpe2fs 1.40.8 (13-Mar-2008)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 4021e5ea-b06d-45c9-8c53-28b0565bb834
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal resize_inode dir_index filetype
extents sparse_super large_file huge_file
Filesystem flags: signed_directory_hash test_filesystem
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 58114048
Block count: 116207103
Reserved block count: 5810355
Free blocks: 11485206
Free inodes: 57967276
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 996
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Filesystem created: Wed Oct 3 01:15:34 2007
Last mount time: Wed Apr 9 19:30:26 2008
Last write time: Wed Apr 9 20:02:38 2008
Mount count: 14
Maximum mount count: 27
Last checked: Thu Feb 28 23:21:45 2008
Check interval: 15552000 (6 months)
Next check after: Wed Aug 27 00:21:45 2008
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: tea
Directory Hash Seed: 89709093-0816-4385-a3fa-164c8564e7d2
Journal backup: inode blocks
Journal size: 128M
next prev parent reply other threads:[~2008-04-09 19:31 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
2008-04-09 19:06 ` Theodore Tso
2008-04-09 19:19 ` supersud501 [this message]
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=47FD16DC.1090502@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