All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@MIT.EDU>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
	linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: fsck errors with fsstress
Date: Fri, 18 Apr 2008 15:24:47 -0400	[thread overview]
Message-ID: <20080418192447.GC25797@mit.edu> (raw)
In-Reply-To: <20080415064733.GA8099@skywalker>

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

      reply	other threads:[~2008-04-18 19:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-15  6:47 fsck errors with fsstress Aneesh Kumar K.V
2008-04-18 19:24 ` Theodore Tso [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080418192447.GC25797@mit.edu \
    --to=tytso@mit.edu \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.