linux-kernel - Re: 2.6.22-rc1 killed my ext3 filesystem cleanly unmounted

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: <1179488826.4305.3.camel@garfield.linsyssoft.com>
Date:	Fri, 18 May 2007 17:17:06 +0530
From:	Kalpak Shah <kalpak@...syssoft.com>
To:	Martin Mokrejs <mmokrejs@...osome.natur.cuni.cz>
Cc:	linux-kernel@...r.kernel.org, ext3-users@...hat.com
Subject: Re: 2.6.22-rc1 killed my ext3 filesystem cleanly unmounted

On Fri, 2007-05-18 at 11:06 +0200, Martin Mokrejs wrote:
> Hi,
>   I just tried the 2.6.22-r1 candidate to test whether some bug I have 
> hit in the past still exists. I did use 2.6.20.6 so far. So, I have 
> cleanly rebooted to use the new kernel, after the machine came up I 
> tried to mess with the bug, and had to reboot again to play with kernel 
> commandline parameters. Unfortunately, on the next reboot fsck was 
> schedules on my filesystem after 38 clean mounts. :( And the problem 
> started. The fsck found some unused inodes, but probably did not know 
> where do they belong to, but it deleted them automagically. Finally, the 
> fsck died because it cannot fine some '..' entry.
> 
> /dev/hda3: Entry '..' in .../??? (5701636) has deleted/unused inode
> 5570561. CLEARED.
> Unconnected directory inode 5570567 (...)
> 
> /dev/hda3: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
>                   (i.e., without -a or -p options)
> 

This means that e2fsck has reached a point where it needs user
intervention. So you should not run e2fsck with -p, -a or -y options.
Look up the e2fsck man page for more on this.

Thanks,
Kalpak.

<< snip >>
>   I do remember recently that possibly one of the system packages in 
> Gentoo installed some kind of a hash into the filesystem, or hashing 
> support, something like that. Sorry, I do not remember the details.
> Am just think what could have made the fsck think there is something 
> wrong.
> 
>   I think IO would like to restore the filesystem to the previous stage 
> before running the fsck. How can I do it? No, I do not have a backup of 
> the filesystem. :(
> 
> I subscribed to the email lists but please send me Cc: anyway. Many thanks.
> Martin
> -
> 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/

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