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

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

Theodore Tso <tytso@....edu> writes:

>> It was about 90s after the message showing the filesystem mounted
>
> Hmm, the most likely cause for that would be if the block group
> descriptors had an incorrect number of free blocks.  But you had just
> run e2fsck -f.

No, sorry I was obviously not clear as to the order of things. First the
system rebooted itself a few seconds after writing an oops (spinlock bad
magic) to syslog and subitting it to kerneloops. On the reboot, the
syslog showed a normal (ie no error and no recovery) mount followed
about 90s later by the error dump I posted. After this, I unmounted the
filesystem and ran 'e2fsck /dev/sdb3' which just replayed the journal
and said the fs was clean. I then ran 'e2fsck -f' which made several
prompts for problems.
--
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