From: Dave Chinner <david@fromorbit.com>
To: aurfalien <aurfalien@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: sizing log - is there a too big?
Date: Thu, 27 Jun 2013 11:48:10 +1000 [thread overview]
Message-ID: <20130627014810.GA29790@dastard> (raw)
In-Reply-To: <55C24454-59E9-4285-9A4C-C4BD24EDBEEC@gmail.com>
On Wed, Jun 26, 2013 at 04:56:31PM -0700, aurfalien wrote:
> Hi all,
>
> Wondering if my log being just under 2GB is a bad idea.
>
> Noticing flush-253:2/kcopyd which is my XFS file system getting
> really high load avg and wait times via top).
What has the log size got to do with something that is happening at
the block layer? What's your storage config?
> Doing a simple rsync over NFS and after a bit, the system gets to a load of 24.... yikes...
Let me guess - 24 nfsds blocked waiting for kcopyd to do it's stuff?
Load average going up when the NFS server is busy generally means
your IO subsystem is heavily loaded - it's not uncommon to see large
NFS servers that are extremely busy sustain load averages over a
100 (or even 1000) for hours/days on end....
> Upon killing the rsync, I am seeing loads going down to sub 1
> after about 10 min. I have repeated this to verify 10 min.
Sure. Processes blocked on IO contribute to the load average. Kill
the IO load, and the load average will return to nothing in 10-15
minutes.
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-06-27 1:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 23:56 sizing log - is there a too big? aurfalien
2013-06-27 1:48 ` Dave Chinner [this message]
2013-06-27 15:58 ` aurfalien
2013-06-28 1:56 ` Dave Chinner
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=20130627014810.GA29790@dastard \
--to=david@fromorbit.com \
--cc=aurfalien@gmail.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