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
| ||
|
Date: Fri, 24 Apr 2009 08:00:04 -0400 From: Theodore Tso <tytso@....edu> To: Christian Kujau <christian@...dbynature.de> Cc: Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org Subject: Re: ext4_ext_check_inode: bad header/extent in inode On Fri, Apr 24, 2009 at 02:40:58AM -0700, Christian Kujau wrote: > > 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. I doubt it; the problem was that the repair performed by e2fsck 1.41.3 was simply imcomplete. You can try to reproduce the corrupted filesystem again, but it should result in the same result. Note that because there was garbage written into the inode table, there was going to be data loss; there's not much that can be done about that. This just simple does a better job cleaning up after the mess, that's all. - Ted -- 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