From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Theodore Tso <tytso@mit.edu>, ext4 <linux-ext4@vger.kernel.org>
Subject: Re: i_size error with the latest patchqueue
Date: Thu, 31 Jul 2008 22:36:13 +0530 [thread overview]
Message-ID: <20080731170613.GC20838@skywalker> (raw)
In-Reply-To: <4891EB43.9080408@redhat.com>
On Thu, Jul 31, 2008 at 11:41:39AM -0500, Eric Sandeen wrote:
> Aneesh Kumar K.V wrote:
> > 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
>
> are those due to blocks beyond EOF, I assume? How is fallocate being
> called in fsstress?
>
lr = ((__int64_t)random() << 32) + random();
off = (off64_t)(lr % MIN(stb.st_size + (1024 * 1024), MAXFSIZE));
off %= maxfsize;
len = (random() % (getpagesize() * 32)) + 1;
#ifdef __i386__
#define __NR_fallocate 324
e = syscall(__NR_fallocate, fd, 0, off, len) < 0 ? errno : 0;
#elif defined (__powerpc__)
#define __NR_fallocate 309
e = syscall(__NR_fallocate, fd, 0, 0, (unsigned int)off, 0, (unsigned int) len) < 0 ? errno : 0;
#elif defined (__x86_64__)
#define __NR_fallocate 285
e = syscall(__NR_fallocate, fd, 0, off, len) < 0 ? errno : 0;
#endif
next prev parent reply other threads:[~2008-07-31 17:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 16:10 i_size error with the latest patchqueue Aneesh Kumar K.V
2008-07-31 16:41 ` Eric Sandeen
2008-07-31 17:06 ` Aneesh Kumar K.V [this message]
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=20080731170613.GC20838@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;
as well as URLs for NNTP newsgroup(s).