From: Dave Chinner <david@fromorbit.com>
To: Spelic <spelic@shiftmail.org>
Cc: xfs@oss.sgi.com
Subject: Re: Xfs delaylog hanged up
Date: Wed, 24 Nov 2010 07:46:09 +1100 [thread overview]
Message-ID: <20101123204609.GW22876@dastard> (raw)
In-Reply-To: <4CEBA2D5.2020708@shiftmail.org>
On Tue, Nov 23, 2010 at 12:17:41PM +0100, Spelic wrote:
> On 11/23/2010 12:29 AM, Dave Chinner wrote:
> >>16 disk MD raid-5
> >What is the storage hardware and the MD raid5 configuration?
>
> Tyan motherboard with 5400 chipset
> dual Xeon E5420
>
> 16 disks on this one:
> 05:00.0 RAID bus controller: 3ware Inc 9650SE SATA-II RAID PCIe (rev 01)
> Subsystem: 3ware Inc 9650SE SATA-II RAID PCIe
> Flags: bus master, fast devsel, latency 0, IRQ 16
> Memory at ce000000 (64-bit, prefetchable) [size=32M]
> Memory at d2600000 (64-bit, non-prefetchable) [size=4K]
> I/O ports at 3000 [size=256]
> [virtual] Expansion ROM at d26e0000 [disabled] [size=128K]
> Capabilities: <access denied>
> Kernel driver in use: 3w-9xxx
> Kernel modules: 3w-9xxx
Hmmmm. We get plenty of reports about problems with 3ware RAID
controllers, many of which are RAID controller problems. Can you
make sure you are running the latest firmware on the controller?
> /# xfs_info /perftest/xfs/
> meta-data=/dev/mapper/perftestvg-xfslv isize=256 agcount=16,
> agsize=50331648 blks
> = sectsz=512 attr=2
> data = bsize=4096 blocks=805306368, imaxpct=5
> = sunit=0 swidth=0 blks
> naming =version 2 bsize=4096 ascii-ci=0
> log =internal bsize=4096 blocks=32768, version=2
> = sectsz=512 sunit=0 blks, lazy-count=0
> realtime =none extsz=4096 blocks=0, rtextents=0
Nothing unusual there.
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...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-11-23 20:44 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 [this message]
2010-11-23 22:14 ` Stan Hoeppner
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=20101123204609.GW22876@dastard \
--to=david@fromorbit.com \
--cc=spelic@shiftmail.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox