linux-ext4 - Re: Block allocation failed

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 19 Aug 2009 10:25:30 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	Graham Murray <graham@...rray.org.uk>
CC:	linux-ext4@...r.kernel.org
Subject: Re: Block allocation failed

Graham Murray wrote:
> Theodore Tso <tytso@....edu> writes:
> 
>> On Wed, Aug 19, 2009 at 06:27:46AM +0100, Graham Murray wrote:
>>> Shortly after rebooting following an untidy shutdown due to an unrelated
>>> (to ext4 or the filesystem) Oops. Unmounting the partition and running
>>> e2fsck (version 1.41.8) just replayed the journal and stated the
>>> filesystem was clean but I did not believe it so ran 'e2fsck -f
>>> /dev/sdb3' and that showed several errors which I allowed it to correct.
>> What sort of errors did it find?
>>
> Sorry, but I do not remember all the errors, it was late at night. The
> first were some sort of block error with lots of block numbers in ()
> which I responded 'y' to fix. 

Probably something like this:

Block bitmap differences:  +(32768--34306) +(65536--66049)
+(98304--99842) +(131072--131585) +(163840--165378) +(196608--197121) ...

indicating corrupt bitmaps I guess, which would explain the later mismatch.

-Eric
--
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