From: Nagy Zoltan <kirk@bteam.hu>
To: David Chinner <dgc@sgi.com>
Cc: David Flynn <davidf@rd.bbc.co.uk>,
daivdf@rd.bbc.co.uk, linux-raid@vger.kernel.org
Subject: Re: xfs+md(raid5) xfssyncd & kswapd & pdflush hung in d-state
Date: Tue, 25 Mar 2008 05:00:34 +0100 [thread overview]
Message-ID: <20080325050034.8df80de0.kirk@bteam.hu> (raw)
In-Reply-To: <20080325032906.GC108924158@sgi.com>
hi,
i've not run thru the whole report - but i think i've experienced the
same problem, the thread is: '2.6.24-rc6 reproducible raid5 hang'
and the solution was for my setup was to upgrade to 2.6.25-rc6
it doesn't occur using other fs - as a quick test you could try out
ext3/jfs
cheers,
kirk
> Added linux-raid to cc - this is not an XFS problem
>
> Cheers,
>
> Dave.
>
> On Wed, Mar 19, 2008 at 03:05:10PM +0000, David Flynn wrote:
> > We are currently experiencing a problem with writing to xfs on a 20disk
> > raid5 array. It seems very similar to a post in 2007nov09:
> >
> > Re: 2.6.23.1: mdadm/raid5 hung/d-state
> >
> > Using kernel 2.6.24. Unlike the previous post the array was in a clean
> > state so no resync was occuring. We are able to read from the array,
> > but any process that writes joins the list of blocked tasks
> >
> > The machine is:
> > 2 of dual core opteron 280
> > 16GiB RAM
> > 4 lots of 5 sata disks connected to sil3124 sata hba.
> > Running 2.6.24
> >
> > There was a single rsync process accessing the array at the time
> > (~40MB/sec).
> >
> > Random other bits[1]:
> > # cat /sys/block/md1/md/stripe_cache_active
> > 256
> > # cat /sys/block/md1/md/stripe_cache_size
> > 256
> >
> > Example of sysrq-w:
> >
prev parent reply other threads:[~2008-03-25 4:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080319150508.GA3087@localhost.localdomain>
2008-03-25 3:29 ` xfs+md(raid5) xfssyncd & kswapd & pdflush hung in d-state David Chinner
2008-03-25 4:00 ` Nagy Zoltan [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=20080325050034.8df80de0.kirk@bteam.hu \
--to=kirk@bteam.hu \
--cc=daivdf@rd.bbc.co.uk \
--cc=davidf@rd.bbc.co.uk \
--cc=dgc@sgi.com \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).