From: Dave Chinner <david@fromorbit.com>
To: yuji_touya@yokogawa-digital.com
Cc: xfs@oss.sgi.com
Subject: Re: 2.6.27.30 fc10, some processes stuck in D state
Date: Thu, 6 Jan 2011 16:00:57 +1100 [thread overview]
Message-ID: <20110106050057.GF8322@dastard> (raw)
In-Reply-To: <8529A87D856C184491994079B5F87B68C1A8289FCC@EXMAIL03.jp.ykgw.net>
On Thu, Jan 06, 2011 at 01:18:27PM +0900, yuji_touya@yokogawa-digital.com wrote:
> Hello folks,
>
> We need to save a bunch of transport-stream(TS) data(4MB/sec, 300GB/day), and
> are using xfs formatted hardware RAID system to save TS data.
> Some processes (pdflush, kswapd, our own services etc) stuck in D-state and
> our system stops saving and down-converting TS data.
Everything is waiting for log space to be freed. Typically a sign
that metadata has not been flushed or that IO completion has not occurred
so the tail is not moving forward.
> It rarely happens (3 times in recent 3 months), but it's quite serious for us.
> How can we avoid this?
What did you change 3 months ago? Or did this always happen?
> One more thing, in that situation when I run "ls /mnt/raid/foo" command,
> all stuck processes suddenly wake up and continue running. Very strange...
> (/mnt/raid is where we mount xfs)
So doing new read IOs starts stuff moving again? That sounds like an IO
completion has not arrived from the lower layers until a new IO is
issued and completes. Perhaps the hardware RAID is not issuing an
interrupt when it should?
What type of RAID controller/storage hardware are you using? Is it
all running the latest firmware, appropriate drivers, etc?
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:[~2011-01-06 4:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 4:18 2.6.27.30 fc10, some processes stuck in D state yuji_touya
2011-01-06 5:00 ` Dave Chinner [this message]
2011-01-07 11:00 ` yuji_touya
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=20110106050057.GF8322@dastard \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
--cc=yuji_touya@yokogawa-digital.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