All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: ext4 <linux-ext4@vger.kernel.org>
Subject: i_size error with the latest patchqueue
Date: Thu, 31 Jul 2008 21:40:59 +0530	[thread overview]
Message-ID: <20080731161058.GA20838@skywalker> (raw)

Hi Ted,

I haven't yet looked at whether it is kernel or e2fsck bug.
But I am having this with the latest patch queue when running
fsstress. The fsstress have falloc added as a supported operation.
So it is mostly to do with fallocate. Architecture is x86.

The tests performed are

               chown 3/39 write op
               creat 4/39 write op
               dread 4/39  
           fdatasync 1/39 write op
               fsync 1/39 write op
            getdents 1/39  
                link 1/39 write op
               mkdir 2/39 write op
               mknod 2/39 write op
                read 1/39  
            readlink 1/39  
              rename 2/39 write op
               rmdir 1/39 write op
                stat 1/39  
             symlink 2/39 write op
                sync 1/39  
            truncate 2/39 write op
              unlink 1/39 write op
               write 4/39 write op
           fallocate 4/39 write op

seed = 1218256896


/usr/local/e2fsprogs/sbin/e2fsck -fnv /dev/sdb1
e2fsck 1.41.0 (10-Jul-2008)
Pass 1: Checking inodes, blocks, and sizes
Inode 10093, i_size is 974599, should be 999424.  Fix? no

Inode 22481, i_size is 363927, should be 909312.  Fix? no

Inode 28621, i_size is 143236, should be 159744.  Fix? no

Inode 28635, i_size is 1203683, should be 1830912.  Fix? no

Inode 42764, i_size is 2328377, should be 2691072.  Fix? no

Inode 54630, i_size is 204182, should be 331776.  Fix? no

Inode 60249, i_size is 0, should be 700416.  Fix? no

Inode 67588, i_size is 1621922, should be 1810432.  Fix? no

Inode 71084, i_size is 0, should be 184320.  Fix? no

Inode 78764, i_size is 0, should be 151552.  Fix? no

Inode 92569, i_size is 651967, should be 806912.  Fix? no


-aneesh

             reply	other threads:[~2008-07-31 16:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31 16:10 Aneesh Kumar K.V [this message]
2008-07-31 16:41 ` i_size error with the latest patchqueue Eric Sandeen
2008-07-31 17:06   ` Aneesh Kumar K.V
2008-07-31 16:47 ` Theodore Tso
2008-07-31 16:51   ` Eric Sandeen
2008-07-31 16:59   ` Aneesh Kumar K.V
2008-07-31 17:08   ` Aneesh Kumar K.V
2008-07-31 18:25     ` Theodore Tso
2008-07-31 18:47       ` 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=20080731161058.GA20838@skywalker \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --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 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.