From: Dave Chinner <david@fromorbit.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: "xfs-masters@oss.sgi.com" <xfs-masters@oss.sgi.com>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Vanilla 3.0.78
Date: Mon, 29 Jul 2013 20:01:34 +1000 [thread overview]
Message-ID: <20130729100134.GH13468@dastard> (raw)
In-Reply-To: <51F62878.4090408@profihost.ag>
On Mon, Jul 29, 2013 at 10:31:52AM +0200, Stefan Priebe - Profihost AG wrote:
> Am 29.07.2013 10:22, schrieb Dave Chinner:
> > On Mon, Jul 29, 2013 at 09:39:37AM +0200, Stefan Priebe - Profihost AG wrote:
> >> Hi,
> >>
> >> while running 3.0.78 and doing heavy rsync tasks on a raid 50 i'm gettig
> >> these call traces:
> >
> > Judging by the timestamps the problem clears and the system keeps
> > running?
>
> Yes.
>
> > If so, the problem is likely to be a combination of contention on a
> > specific AG for allocation and slow IO. Given it is RAID 50, it's
> > probably really slow IO, and probably lots of threads wanting the
> > lock and queuing up on it.
> >
> > What's 'iostat -m -x -d 5' look like when these messages are dumped
> > out?
>
> Don't have that but some nagios stats. There were 1000 iop/s and 8MB/s.
Yup, that sounds like it was doing lots of small random IOs and
hence was IO bound...
> But i can reduce the tasks done in parallel if this is the problem.
Try and find out what the average IO times were when the messages
are being emitted. If that's up in the seconds, then it's a good
chance you are simply throwing too many small IOs at your storage.
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:[~2013-07-29 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 7:39 Vanilla 3.0.78 Stefan Priebe - Profihost AG
2013-07-29 8:22 ` Dave Chinner
2013-07-29 8:31 ` Stefan Priebe - Profihost AG
2013-07-29 10:01 ` Dave Chinner [this message]
2013-07-29 11:02 ` Stefan Priebe - Profihost AG
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=20130729100134.GH13468@dastard \
--to=david@fromorbit.com \
--cc=s.priebe@profihost.ag \
--cc=xfs-masters@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox