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]

Message-ID: <87zl9vhnfa.fsf@newton.gmurray.org.uk>
Date:	Wed, 19 Aug 2009 15:46:01 +0100
From:	Graham Murray <graham@...rray.org.uk>
To:	linux-ext4@...r.kernel.org
Subject: Re: Block allocation failed

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. Then there were a number of files with
multiply-claimed blocks which I responded 'y' to clone. There were files
containing unallocated or deleted inodes. A number of files were
recovered to Lost+Found. A number of inode reference counts were
wrong. There may have been other errors, but I do not remember what they
were. 

>> Aug 18 23:50:07 newton EXT4-fs error (device sdb3): ext4_mb_generate_buddy: EXT4-fs: group 35: 3499 blocks in bitmap, 3243 in gd
>> Aug 18 23:50:07 newton Aborting journal on device sdb3:8.
>
> Was this right after you mounted the filesystem, or did some time
> take place before these errors started showing up?

It was about 90s after the message showing the filesystem mounted

Aug 18 23:48:33 newton EXT4-fs (sdb3): barriers enabled
Aug 18 23:48:33 newton kjournald2 starting: pid 3855, dev sdb3:8, commit
interval 10 seconds
Aug 18 23:48:33 newton EXT4-fs (sdb3): internal journal on sdb3:8
Aug 18 23:48:33 newton EXT4-fs (sdb3): delayed allocation enabled
Aug 18 23:48:33 newton EXT4-fs: file extents enabled
Aug 18 23:48:33 newton EXT4-fs: mballoc enabled
Aug 18 23:48:33 newton EXT4-fs (sdb3): mounted filesystem with ordered
data mode

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