[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200908300025.48034.edt@aei.ca>
Date: Sun, 30 Aug 2009 00:25:47 -0400
From: Ed Tomlinson <edt@....ca>
To: linux-kernel@...r.kernel.org
Cc: linux-ext4@...r.kernel.org
Subject: Ext4 corruption that will not go away
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?
TIA,
Ed Tomlinson
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists