From: Stan Hoeppner <stan@hardwarefreak.com>
To: Richard Ems <richard.ems@cape-horn-eng.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS unlink still slow on 3.1.9 kernel ?
Date: Tue, 14 Feb 2012 17:10:34 -0600 [thread overview]
Message-ID: <4F3AE9EA.1050609@hardwarefreak.com> (raw)
In-Reply-To: <4F3A5B49.6020803@cape-horn-eng.com>
On 2/14/2012 7:02 AM, Richard Ems wrote:
> Hi Stan,
>
> I was not subscribed to the list so I did not get your mail. I
Ahh, my bad. I should have done a reply-all. I sometimes forget XFS is
an open list.
> subscribed now, but apparently and admin has to aprove the subscription
> since I am not getting any confirmation email. so this will take some time.
>
>> On 2/13/2012 10:57 AM, Richard Ems wrote:
>>> The case is connected through SCSI.
>>
>> Do you mean iSCSI? Does the host on which you're running your "find
>> dir" command have a 1GbE or 10GbE connection to the InforTrend unit?
>> More than one connection using bonding or multipath? Direct connected
>> or through a switch(es)? What brand is the switch(es)? Switch(es)
>> under heavy load?
>
> NO. SCSI. Not iSCSI. No switches, it's direct attached through a LSI
> SCSI Controller:
Ok so it's obviously not a host bandwidth or latency issue then. I was
just trying to cover the all the bases with my hardware questions.
Also I didn't realize anyone was (still?) offering parallel SCSI host
connections on their SATA arrays.
> lspci shows:
>
> LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI
PCI-X? So this host and array have a few years on them I assume.
>> Also check the performance data in the management interface on the
>> InforTrend unit to see if you're hitting any limits there (if it has
>> such a feature). RAID6 is numerically intensive and that particular
>> controller may not have the ASIC horsepower to keep up with the IOPS
>> workload you're throwing at it.
>
> There is no performance data in the management interface to check.
Ok, so this is a relatively basic, entry level array?
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-02-14 23:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 13:02 XFS unlink still slow on 3.1.9 kernel ? Richard Ems
[not found] ` <4F3AA191.9030606@mnsu.edu>
2012-02-14 18:12 ` Richard Ems
2012-02-14 19:07 ` Christoph Hellwig
2012-02-15 12:48 ` Richard Ems
2012-02-14 23:10 ` Stan Hoeppner [this message]
2012-02-15 15:54 ` Richard Ems
-- strict thread matches above, loose matches on Subject: below --
2012-02-13 16:57 Richard Ems
2012-02-13 17:08 ` Christoph Hellwig
2012-02-13 17:11 ` Richard Ems
2012-02-13 17:15 ` Christoph Hellwig
2012-02-13 17:26 ` Richard Ems
2012-02-13 17:29 ` Christoph Hellwig
2012-02-13 17:53 ` Richard Ems
2012-02-13 18:02 ` Christoph Hellwig
2012-02-13 18:06 ` Richard Ems
2012-02-13 18:10 ` Christoph Hellwig
2012-02-13 18:18 ` Richard Ems
2012-02-13 18:48 ` Richard Ems
2012-02-13 21:16 ` Christoph Hellwig
2012-02-14 5:31 ` Stan Hoeppner
2012-02-14 9:48 ` Richard Ems
2012-02-14 19:43 ` Christoph Hellwig
2012-02-14 9:49 ` Richard Ems
2012-02-14 10:54 ` Richard Ems
2012-02-14 11:44 ` Richard Ems
2012-02-14 0:09 ` Dave Chinner
2012-02-14 12:32 ` Richard Ems
2012-02-14 19:45 ` Christoph Hellwig
2012-02-15 12:07 ` Richard Ems
2012-02-15 1:27 ` Dave Chinner
2012-02-15 12:07 ` Richard Ems
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=4F3AE9EA.1050609@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=richard.ems@cape-horn-eng.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.