From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: Xfs delaylog hanged up
Date: Tue, 23 Nov 2010 16:14:16 -0600 [thread overview]
Message-ID: <4CEC3CB8.8000509@hardwarefreak.com> (raw)
In-Reply-To: <20101123204609.GW22876@dastard>
Dave Chinner put forth on 11/23/2010 2:46 PM:
> I've been unable to reproduce the problem with your test case (been
> running over night) on a 12-disk, 16TB dm RAID0 array, but I'll keep
> trying to reproduce it for a while. I note that the load is
> generating close to 10,000 iops on my test system, so it may very
> well be triggering load related problems in your raid controller...
Somewhat off topic, but how are you generating 10,000 IOPS by carving a
16TB LUN/volume from 12 x 2TB SATA disk spindles? Such drives aren't
even capable of 200 seeks per second. Even if they were you'd top out
at less than 2,500 IOPS (random). 16TB/12=1.33 TB per disk. No such
capacity disk exists. So I assume you're using 12 x 2TB disks and
slicing/dicing out 16TB. What am I missing Dave?
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-11-23 22:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 19:27 Xfs delaylog hanged up Spelic
2010-11-22 23:29 ` Dave Chinner
2010-11-23 11:17 ` Spelic
2010-11-23 13:28 ` Spelic
2010-11-23 20:46 ` Dave Chinner
2010-11-23 22:14 ` Stan Hoeppner [this message]
2010-11-24 0:20 ` Dave Chinner
2010-11-24 13:12 ` Spelic
2010-11-24 21:50 ` Dave Chinner
2010-11-23 22:48 ` Emmanuel Florac
2010-11-24 0:36 ` Spelic
2010-11-24 1:40 ` Stan Hoeppner
2010-11-24 6:18 ` Michael Monnerie
2010-11-24 7:44 ` Emmanuel Florac
2010-11-24 0:58 ` Spelic
2010-11-24 5:44 ` Dave Chinner
2010-11-25 23:34 ` Spelic
2010-11-26 4:20 ` Dave Chinner
2010-11-24 22:52 ` Spelic
2010-11-26 22:43 ` Spelic
-- strict thread matches above, loose matches on Subject: below --
2010-11-24 4:03 Richard Scobie
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=4CEC3CB8.8000509@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=xfs@oss.sgi.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 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.