| 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
| ||
|
Message-ID: <62b0912f0608090336g574d957dk33bf554691518689@mail.gmail.com> Date: Wed, 9 Aug 2006 12:36:13 +0200 From: "Molle Bestefich" <molle.bestefich@...il.com> To: linux-kernel@...r.kernel.org Cc: sergio@...giomb.no-ip.org Subject: Re: ext3 corruption Molle Bestefich wrote: > I have a ~1TB filesystem that fails to mount, the message is: > > EXT3-fs error (device loop0): ext3_check_descriptors: Block bitmap for > group 2338 not in group (block 1607003381)! > EXT3-fs: group descriptors corrupted ! > > A day before, it worked flawlessly. > > What could have happened, and what's the best course of action? I should probably mention that I've been bitten by e2fsck before. I had a filesystem with minor damage, but after running e2fsck it was completely nuked. Nothing was recoverable. So before anyone suggest running e2fsck, I'd really like someone knowledgeable to tell me what e2fsck is going to do about "group descriptors corrupted" *BEFORE* I go ahead and blindly run it. - 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