linux-ext4 - Re: Ext4 corruption that will not go away

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200908301919.56608.edt@aei.ca>
Date:	Sun, 30 Aug 2009 19:19:55 -0400
From:	Ed Tomlinson <edt@....ca>
To:	nicholas.dokos@...com
Cc:	linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org
Subject: Re: Ext4 corruption that will not go away

On Sunday 30 August 2009 10:24:56 Nick Dokos wrote:
> > Hi,
> > 
> > I am running 2.6.31-rc8+ and have ext4 corruption that will not go away.
> > 
> > My root fs is ext4 on sdb3.  I have moved the directory with corruption into lost+found and booted to a rescuse
> > system (arch linux) and run fsck.ext4 on the filesystem, which then reports its clean...  Booting back into my
> > gentoo system and attempting to remove the xx directory from lost+found gives:
> > 
> > [  172.408799] EXT4-fs error (device sdb3): ext4_ext_check_inode: bad header/extent in inode #706801: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)                                                                                                
> > [  172.429410] EXT4-fs error (device sdb3): ext4_ext_check_inode: bad header/extent in inode #706801: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)                                                                                                
> > [  172.449920] EXT4-fs error (device sdb3): ext4_ext_check_inode: bad header/extent in inode #706801: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
> > 
> > The above is repeatable.
> > 
> > How can I _really_ clean this fs?  What info is needed to help the process?
> > 
> 
> The first two pieces of information needed would be the version of e2fsprogs
> that you are running (e2fsck -V) and the stat of inode 706801:
> 
>   debugfs -R 'stat <706801>' /dev/sdb3
> 

e2fsck 1.41.9 (22-Aug-2009)
        Using EXT2FS Library version 1.41.9, 22-Aug-2009

Inode: 706801   Type: regular    Mode:  0644   Flags: 0x80000
Generation: 28075061    Version: 0x00000000:00000001
User:     0   Group:     0   Size: 1442
File ACL: 0    Directory ACL: 0
Links: 1   Blockcount: 0
Fragment:  Address: 0    Number: 0    Size: 0
 ctime: 0x4a8beb6a:a8c2e6e4 -- Wed Aug 19 08:09:14 2009
 atime: 0x4a8beb6a:00000000 -- Wed Aug 19 08:09:14 2009
 mtime: 0x4a8b17d9:00000000 -- Tue Aug 18 17:06:33 2009
crtime: 0x4a8beb6a:9e456724 -- Wed Aug 19 08:09:14 2009
Size of extra inode fields: 28
EXTENTS:

and of 76804 which also has a problem

Inode: 706804   Type: regular    Mode:  0644   Flags: 0x80000
Generation: 4140131203    Version: 0x00000000:00000001
User:  1000   Group:   100   Size: 523
File ACL: 0    Directory ACL: 0
Links: 1   Blockcount: 0
Fragment:  Address: 0    Number: 0    Size: 0
 ctime: 0x4a95c957:348db0b8 -- Wed Aug 26 19:46:31 2009
 atime: 0x4a991f2b:cf3a606c -- Sat Aug 29 08:29:31 2009
 mtime: 0x4a95c957:348db0b8 -- Wed Aug 26 19:46:31 2009
crtime: 0x4a95c957:348db0b8 -- Wed Aug 26 19:46:31 2009
Size of extra inode fields: 28
EXTENTS:

Hope this helps
Ed
--
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