linux-ext4 - Re: fsck errors with fsstress

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]

Date:	Fri, 18 Apr 2008 15:24:47 -0400
From:	Theodore Tso <tytso@....EDU>
To:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Cc:	Eric Sandeen <sandeen@...hat.com>,
	linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: fsck errors with fsstress

On Tue, Apr 15, 2008 at 12:17:33PM +0530, Aneesh Kumar K.V wrote:
> 
> On x86_64 after fsstress with fallocate is run with 
> 
> fsstress -c -n1000 -p1000 -d /mnt/tmp/fsstress -f dwrite=0
> 
> e2fsprogs from next branch with HEAD at v1.40.8-163-g60dc00b
> 
> /usr/local/e2fsprogs/sbin/e2fsck -fnv /dev/sda5
> e2fsck 1.40.8 (13-Mar-2008)
> Pass 1: Checking inodes, blocks, and sizes
> Inode 401326 has an invalid extent
> 	(logical block 76, physical block 2441549, invalid len 711)
> Clear? no

I think this was fixed by Eric's patch:

    e2fsck: Only check PR_1_EXTENT_ENDS_BEYOND for leaf nodes

I've integrated this and pushed it out into the latest 'pu' branch.

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