linux-ext4 - Re: e2fsck not fixing all corruptions on the first run?

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: <alpine.DEB.1.00.0803132219590.7433@sheep.housecafe.de>
Date:	Thu, 13 Mar 2008 22:22:25 +0100 (CET)
From:	Christian Kujau <lists@...dbynature.de>
To:	Theodore Tso <tytso@....edu>
cc:	linux-ext4@...r.kernel.org
Subject: Re: e2fsck not fixing all corruptions on the first run?

On Thu, 13 Mar 2008, Theodore Tso wrote:
>> http://nerdbynature.de/bits/e2fsprogs.pu/md4.log
>> http://nerdbynature.de/bits/e2fsprogs.pu/
>
> Hmm.  What I really need is *first* e2fsck run, to see what it did.

The md4.log is the first e2fsck run:

1) mounted fs, noticed error message in dmesg
2) umounted fs
3) ran e2fsck, right on top of this md4.log file...

The 2nd run is the one after the "/dev/md4: clean" message in md4.log

Thanks,
Christian.
-- 
BOFH excuse #265:

The mouse escaped.
--
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