public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Eric Sandeen <sandeen@redhat.com>, Theodore Tso <tytso@mit.edu>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: fsck errors with fsstress
Date: Tue, 15 Apr 2008 12:17:33 +0530	[thread overview]
Message-ID: <20080415064733.GA8099@skywalker> (raw)

Hi,

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

Inode 401326, i_blocks is 1112, should be 0.  Fix? no

Inode 475743 has an invalid extent
	(logical block 226, physical block 2441673, invalid len 245)
Clear? no

Inode 475743, i_blocks is 328, should be 0.  Fix? no

Inode 603723 has an invalid extent
	(logical block 34, physical block 2441671, invalid len 316)
Clear? no

Inode 603723, i_blocks is 456, should be 0.  Fix? no

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -(118168--118173) -(174537--174541) -(371445--371462) -(592857--592859) -937329 -(961360--961363) -(968529--968547) -(1238135--1238143) -(1285426--1285432) -(1415800--1415801) -(1576655--1576681) -(2075764--2075776) -(2364415--2364420) -(2368402--2368410) -(2432102--2432111) -2432247 -(2433343--2433346) -(2435405--2435432) -(2441075--2441105) -(2441265--2441289) -(2441348--2441353) -2441549 -2441671 -2441673
Fix? no


/dev/sda5: ********** WARNING: Filesystem still has errors **********

             reply	other threads:[~2008-04-15  6:48 UTC|newest]

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

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=20080415064733.GA8099@skywalker \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox