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.0803132255230.7433@sheep.housecafe.de>
Date:	Thu, 13 Mar 2008 22:59:55 +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:
> Oh, right.  Sorry, I missed that.  I think I know what's going on.
> The problem is we're not supporting long symlinks which are in extents
> format.  That's something which we changed, but we're going to change
> back (since we need it to support filesystems with > 2**32 blocks).

When you say "changed", you mean the on-disk format changed? If so, I 
could (should?) just mkfs again, since ext4 is in flux anyway and nobody 
said the on-disk format was frozen. IOW, I don't know if it's wise to put 
in quirks just because of some old test-environment. When ext4 is 
(offically) released, everybody will have the "right" format and e2fsck 
will work as expected, no?

thanks,
C.
-- 
BOFH excuse #441:

Hash table has woodworm
--
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