From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Dmitri Monakhov <dmonakhov@openvz.org>
Cc: Eric Sandeen <sandeen@redhat.com>, Mingming Cao <cmm@us.ibm.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: Problem with fsstress on powerpc
Date: Wed, 9 Apr 2008 13:51:15 +0530 [thread overview]
Message-ID: <20080409082115.GA8238@skywalker> (raw)
In-Reply-To: <20080409074457.GB944@dmon-lap.sw.ru>
On Wed, Apr 09, 2008 at 11:44:57AM +0400, Dmitri Monakhov wrote:
> On 20:54 Tue 08 Apr , Aneesh Kumar K.V wrote:
> > Hi All,
> >
> > Test case: fsstress with fallocate test case added.
> This may happens because of direct write.
> Please add exact fsstess command and options.
> >
fsstress -c -n1000 -p1000 -d /mnt/tmp/
What i found was also related. The file which had errors had the below
operations on them.
82/901: dread d16/d20/d22/d2d/d63/d68/d9a/f93 [622592,53248] 0
82/939: dwrite d16/d20/d22/d2d/d63/d68/d9a/f93 [1093632,77824] 28
9/863: fallocate d1/d2d/d32/d8f/d97/d108/d9b/ffb [2041,75851] 28
18/733: fallocate d9/ddd/f86 [481025,18486] 0
18/735: dwrite d9/ddd/f86 [679936,36864] 0
18/764: dread d9/ddd/f86 [53248,8192] 0
18/910: dwrite d9/ddd/f86 [1454080,4096] 28
18/999: dwrite d9/ddd/f86 [1798144,61440] 28
But what would happen during direct write that cause this ?
-aneesh
next prev parent reply other threads:[~2008-04-09 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 15:24 Problem with fsstress on powerpc Aneesh Kumar K.V
2008-04-09 7:44 ` Dmitri Monakhov
2008-04-09 8:21 ` Aneesh Kumar K.V [this message]
2008-04-09 8:33 ` Dmitri Monakhov
2008-04-09 9:39 ` Aneesh Kumar K.V
2008-04-09 10:01 ` Dmitri Monakhov
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=20080409082115.GA8238@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=dmonakhov@openvz.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox