From: udit agarwal <fzdudit@gmail.com>
To: ceph-devel@vger.kernel.org
Subject: Re: iozone test crashed on ceph
Date: Wed, 6 Jun 2012 02:31:56 +0000 (UTC) [thread overview]
Message-ID: <loom.20120606T041909-114@post.gmane.org> (raw)
In-Reply-To: CADvuQRHMxM9PxOyxmej9_MuJajGNV2=yBxL9vN7P4KEvA7US5A@mail.gmail.com
Hi,
Thanks for your reply.
After you hinted that this problem may have caused due to using record size of
length 4k. Then, I ran iozone test on a 5m file with record length 4k and to my
surprise, the ceph system again hanged up. Then, I tried same with record
lengths from 8k to 1m and everything worked fine for these cases with 5 MB file.
Now, I have already executed the iozone test with 5G file and with record sizes
from 8k to 16m and will see what happens!!
--Udit Agarwal
next prev parent reply other threads:[~2012-06-06 2:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 0:58 iozone test crashed on ceph udit agarwal
2012-06-01 2:15 ` Sam Just
2012-06-01 4:05 ` udit agarwal
2012-06-01 16:32 ` Greg Farnum
2012-06-04 21:52 ` udit agarwal
2012-06-04 22:42 ` Tommi Virtanen
2012-06-04 23:39 ` udit agarwal
2012-06-04 23:43 ` udit agarwal
2012-06-05 16:45 ` Tommi Virtanen
2012-06-06 2:31 ` udit agarwal [this message]
2012-06-06 4:15 ` udit agarwal
2012-06-06 16:17 ` Tommi Virtanen
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=loom.20120606T041909-114@post.gmane.org \
--to=fzdudit@gmail.com \
--cc=ceph-devel@vger.kernel.org \
/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