From: Jens Axboe <jens.axboe@oracle.com>
To: Girish Satihal <girish.satihal@yahoo.com>
Cc: fio@vger.kernel.org
Subject: Re: Recent changes
Date: Mon, 20 Apr 2009 20:05:55 +0200 [thread overview]
Message-ID: <20090420180555.GH4593@kernel.dk> (raw)
In-Reply-To: <841550.37802.qm@web63802.mail.re1.yahoo.com>
On Mon, Apr 20 2009, Girish Satihal wrote:
>
> Hi Jens,
> This build is the latest build after version 1.24. This build was the
> outcome of the request for adding blockalign/ba option. Can you please
> help in resolving this issue of sequential writes on ext3 file system?
I'd love to help you, but you have to help me a bit as well. I asked you
for a job file that reproduces the problem. If you can send me such a
job file (preferably cut down to just a single section that exhibits the
problem), then I can probably find the error quickly.
>
> Thanks,
> Girish
>
>
> --- On Sat, 4/18/09, Jens Axboe <jens.axboe@oracle.com> wrote:
>
> > From: Jens Axboe <jens.axboe@oracle.com>
> > Subject: Re: Recent changes
> > To: "Girish Satihal" <girish.satihal@yahoo.com>
> > Cc: fio@vger.kernel.org
> > Date: Saturday, April 18, 2009, 11:18 PM
> > On Fri, Apr 17 2009, Girish Satihal wrote:
> > > Hi Jens,
> > > I am seeing a serious problem with fio testing. I
> > tried running fio
> > > test on ext3 partition with Sequential Reads and
> > Writes. I keep
> > > getting the I/O write error for Sequential writes. I
> > tried with
> > > multiple servers with different controllers and I
> > still get the same
> > > error. With Sequential Reads and Random Reads/Writes
> > there is no issue
> > > seen. Please find the attached fio results file for
> > Sequential
> > > Reads/Writes which has the error details pertaining to
> > Sequential
> > > writes on ext3 file system. Thanks, Girish
> >
> > That's pretty strange. Your test job(s) seem pretty
> > massive, you don't
> > happen to have a cut down version that exhibits the
> > problem?
> >
> > There also seems to be parts of the error missing from
> > io_u_log_error(),
> > like the file associated with the error and the io_u
> > details (offset=
> > and buflen=, for instance).
> >
> > What version of fio are you using?
> >
> > --
> > Jens Axboe
> >
> > --
> > To unsubscribe from this list: send the line
> > "unsubscribe fio" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at
> > http://vger.kernel.org/majordomo-info.html
>
>
>
--
Jens Axboe
next prev parent reply other threads:[~2009-04-20 18:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090409040002.0D18237A271@kernel.dk>
2009-04-17 21:38 ` Recent changes Girish Satihal
2009-04-18 17:48 ` Jens Axboe
2009-04-20 14:42 ` Girish Satihal
2009-04-20 18:05 ` Jens Axboe [this message]
2009-04-20 20:54 ` Girish Satihal
2009-04-21 5:28 ` Jens Axboe
2009-04-21 7:47 ` Jens Axboe
2009-04-21 15:46 ` Girish Satihal
2009-04-21 19:15 ` Jens Axboe
2009-04-21 22:17 ` Girish Satihal
2009-04-22 5:46 ` Jens Axboe
2009-04-22 5:53 ` Gurudas Pai
2009-04-22 16:46 ` Girish Satihal
2009-04-22 17:40 ` Jens Axboe
[not found] <869776.96350.qm@web63807.mail.re1.yahoo.com>
2009-04-24 4:40 ` Gurudas Pai
2010-11-06 5:00 Jens Axboe
[not found] <20110114050004.0ECBF37A2F4@kernel.dk>
2011-01-14 11:38 ` Bruce Cran
2011-01-14 11:41 ` Jens Axboe
[not found] <20110127050004.1AE9737A304@kernel.dk>
2011-01-27 8:51 ` Bruce Cran
2011-01-27 9:08 ` Jens Axboe
[not found] <20110125050003.F378B37A302@kernel.dk>
2011-01-27 21:08 ` Steven Pratt
2011-01-27 21:12 ` Jens Axboe
2011-01-27 22:06 ` Bruce Cran
2011-01-28 8:28 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2011-10-14 4:00 Jens Axboe
[not found] <20120406040004.1BF99484001@kernel.dk>
2012-04-06 4:29 ` Danny Kukawka
2012-04-06 13:31 ` Jens Axboe
2012-04-06 17:40 ` Danny Kukawka
2012-04-06 17:44 ` Jens Axboe
2012-04-14 6:45 ` Danny Kukawka
2012-04-14 14:47 ` Jens Axboe
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=20090420180555.GH4593@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=fio@vger.kernel.org \
--cc=girish.satihal@yahoo.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