linux-ext4 - Re: ext4 - error with root drive mount

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090204093420.44cac139@amd64linuxmsi.rentzhouse.lan>
Date:	Wed, 4 Feb 2009 09:34:20 -0500
From:	Jimmy Rentz <jedynamic@...lsouth.net>
To:	Theodore Tso <tytso@....edu>
Cc:	Jimmy Rentz <jedynamic@...lsouth.net>, linux-ext4@...r.kernel.org
Subject: Re: ext4 - error with root drive mount

On Wed, 4 Feb 2009 01:24:00 -0500
Theodore Tso <tytso@....edu> wrote:

> On Tue, Feb 03, 2009 at 07:15:31PM -0500, Jimmy Rentz wrote:
> > 	I am unable to mount my ext4 root drive. 
> > 
> > 	I get this error:
> > 	EXT4-fs: ext4_check_descriptors: Block bitmap for group 2688
> > 	not in group (block 4205711663)!<3>EXT4-fs: group
> > descriptors corrupted!
> > 
> > 	I had a similar error some time ago, but I thought it was
> > power related.  I fixed the problem by running a fcsk.  
> 
> You'll need to fix it using fsck again.  I assume the back up
> superblocks will have the correct value.
> 
> It would be interesting to see if there are any other errors picked up
> by e2fsck.
I reran fsck and that fixed the problem. 

Here is a sample of the errors:
Free blocks count wrong for group #1 (14705, counted=19112).
Fix? no

Free blocks count wrong for group #2 (12753, counted=11404).
Fix? no

Free blocks count wrong for group #3 (20531, counted=17213).
Fix? no
...
Free blocks count wrong for group #11160 (7673, counted=3577).

Then some errors about inode and directory counts wrong.

I also forgot that I have a log of the fsck errors when I
had this problem before.

> 
> > 	Any tips to debug this?
> 
> Can you reliably replicate this problem?  I've not seen any similar
> reports of problems like this.
> 
> 						- Ted

I am not sure how to reproduce this problem.  It seems random
enough.  The system is a mythtv box so it happens to
poweron/poweroff on a regular basis to record.    
--
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