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

Message-ID: <alpine.DEB.1.00.0803140815520.7433@sheep.housecafe.de>
Date:	Fri, 14 Mar 2008 08:17:02 +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:
> Technically, I guess you could say the on-disk format changed, but as
> I mentioned, it's going to change back to the original format.  It's
> not a big deal.  The question is for long symlinks, where the symlink
> can't fit in the 60 bytes in the i_block[] array, whether the block
> number should be encoded as a single integer as i_block[0], as it is
> under ext3, or whether it should be encoded as an extents structure.

Thanks again for the explanation (and for the fix, I shall try it soon)!

Christian.
-- 
BOFH excuse #399:

We are a 100% Microsoft Shop.
--
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