public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: xfs@oss.sgi.com
Subject: Re: XFS write speed down
Date: Fri, 30 Apr 2010 11:11:06 +1000	[thread overview]
Message-ID: <20100430011106.GA32515@dastard> (raw)
In-Reply-To: <alpine.LSU.2.01.1004292322530.23248@obet.zrqbmnf.qr>

On Thu, Apr 29, 2010 at 11:46:33PM +0200, Jan Engelhardt wrote:
> Hi,
> 
> Running 2.6.33.2, I am observing this 
> 
> used-xfs$ time ( tar -xf /dev/shm/linux-2.6.33.3.tar ; sync )
> real    12m29.272s
> user    0m0.196s
> sys     0m3.028s

What was the last kernel you ran that didn't have this slowdown?
I see the same test on 2.6.32 to my 2.6TB RAID6 volume take
about 35s.

Can you post the output of "echo w > /proc/sysrq-trigger" while
your test is running?

Cheers,

Dave.

-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2010-04-30  1:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29 21:46 XFS write speed down Jan Engelhardt
2010-04-30  1:11 ` Dave Chinner [this message]

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=20100430011106.GA32515@dastard \
    --to=david@fromorbit.com \
    --cc=jengelh@medozas.de \
    --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