linux-ext4 - Re: Possible ext4 corruption

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: <20090310204418.GW3199@webber.adilger.int>
Date:	Tue, 10 Mar 2009 14:44:18 -0600
From:	Andreas Dilger <adilger@....com>
To:	Kevin Shanahan <kmshanah@...b.org.au>
Cc:	Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org
Subject: Re: Possible ext4 corruption - ACL related?

On Mar 10, 2009  22:45 +1030, Kevin Shanahan wrote:
> hermes:~# e2fsck -pfv /dev/dm-0 
> /dev/dm-0: Inode 865 is in use, but has dtime set.  FIXED.
> /dev/dm-0: Inode 865 has a extra size (33096) which is invalid
> FIXED.
> /dev/dm-0: Inode 865 has INDEX_FL flag set but is not a directory.
> HTREE INDEX CLEARED.
> /dev/dm-0: Inode 865, i_size is 11708523728200260508, should be 0.  FIXED.
> /dev/dm-0: Inode 865, i_blocks is 3851901040, should be 0.  FIXED.

These all mean the inode is garbage.  The Lustre e2fsprogs has a patch
"e2fsprogs-badness_counter" that tracks the number of errors hit in
the inode, and clears it if it appears to be garbage (as in your case),
instead of turning a pile of manure into neatly organized fertilizer.

> Pass 2: Checking directory structure
> Inode 867 (/local/apps/Gestalt.Net/SetupCD/program files/Business Objects/Common/3.5/bin/Cdo32sv.dll) has invalid mode (0152404).
> Clear<y>? yes

This is just more indication of the inodes being corrupted.

> Pass 3: Checking directory connectivity
> Pass 3A: Optimizing directories
> Error reading block 2705859237 (Invalid argument).  Ignore error<y>? yes
> 
> Force rewrite<y>? yes
> 
> Error writing block 2705859237 (Invalid argument).  Ignore error<y>? yes

Hmm, is this read beyond EOF?  The block pointers should be fixed by this
time, so there may be a hole in e2fsck at this point.  I assume you do
not have a 10TB filesystem here.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

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