[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.01.0904240235020.6162@bogon.housecafe.de>
Date: Fri, 24 Apr 2009 02:40:58 -0700 (PDT)
From: Christian Kujau <christian@...dbynature.de>
To: Theodore Tso <tytso@....edu>
cc: Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: ext4_ext_check_inode: bad header/extent in inode
On Fri, 24 Apr 2009, Christian Kujau wrote:
> On Thu, 23 Apr 2009, Theodore Tso wrote:
> > It's been fixed in e2fpsrogs 1.41.5, which I've only just released.
> > It's available on git, sourceforge, and all of the other usual places.
> > This should fix the problem for you.
I got it from sourceforge now and it did indeed "do" something:
sid:~# /opt/e2fsprogs/sbin/fsck.ext4 -v /dev/md0
e2fsck 1.41.5 (23-Apr-2009)
/dev/md0 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
i_file_acl_hi for inode 12042 (/lost+found/#12042) is 64578, should be zero. Clear? yes
i_file_acl_hi for inode 12207 (/lost+found/#12207) is 5, should be zero Clear? yes
i_file_acl_hi for inode 12249 (/lost+found/#12249) is 5, should be zero.Clear? yes
i_file_acl_hi for inode 12090 (/t/#12090) is 5932, should be zero. Clear? yes
...but the "Input/output error" persist :-\
Full scriptlog: http://nerdbynature.de/bits/2.6.30-rc2/scriptlog2.txt
Maybe the repair with 1.41.{3,4} before did something wrong and I should
use 1.41.5 from the beginning? This issue is somewhat reproducible (given
the fs holds enough files), so I could start over, corrupt the fs again
and let e2fsprogs-1.41.5 do the whole job.
Christian.
--
Bruce Schneier does not leak information on the EM spectrum: he emits the theme
to The Good, The Bad, and The Ugly.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists