From: Neil Brown <neilb@suse.de>
To: Tim Small <tim@seoss.co.uk>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Deadlock in md barrier code? / RAID1 / LVM CoW snapshot + ext3 / Debian 5.0 - lenny 2.6.26 kernel
Date: Wed, 22 Sep 2010 08:30:39 +1000 [thread overview]
Message-ID: <20100922083039.283ccdfd@notabene> (raw)
In-Reply-To: <4C991D61.1040400@seoss.co.uk>
On Tue, 21 Sep 2010 22:02:25 +0100
Tim Small <tim@seoss.co.uk> wrote:
> Tim Small wrote:
> > http://buttersideup.com/files/md-raid1-lockup-lvm-snapshot/iodeadlock-sysrq-t.txt
> >
> > ... this was soon after the io to md2 stopped - md0 seems fine...
> >
> > oldshoreham:~# cat /proc/mdstat
> > Personalities : [raid1]
> > md2 : active raid1 sda6[0] sdb6[1]
> > 404600128 blocks [2/2] [UU]
> > [>....................] resync = 0.1% (437056/404600128)
> > finish=343321.2min speed=19K/sec
> >
> >
> > ... I also tried an older Debian 5.0.x kernel from Mar 2009, which is a
> > less-patched 2.6.26, and got the same results. 2.6.32 hasn't deadlocked
> > after 10 minutes (2.6.26 usually does within a minute of boot-up), so
> > I'll leave it re-syncing overnight...
> >
>
> 2.6.32 resynced to completion, but if possible I'd really like to get
> 2.6.26 running on this box, as it uses openvz, and the 2.6.32 openvz
> patches are still pretty green, I think. Is their anything in the
> sysrq-t output in that link of any use? Are there any patches I should
> try, or would it be better to start bisecting between 2.6.26 and 2.6.32
> (assuming I can reproduce the problem without the load pattern which
> openvz is producing - which I probably can).
>
> Cheers,
>
> Tim.
>
>
It is odd that 2.6.32 works and 2.6.26 doesn't as I cannot find any change
between the two that could be related.
There were some deadlock issues if a read-error was detected during resync
but I don't think you are getting read errors are you?
A bisect would of course be easier for me, though not particularly easy for
you....
Maybe if you can get me a full sysrq-T list that might help.
NeilBrown
next prev parent reply other threads:[~2010-09-21 22:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 14:53 Deadlock in md barrier code? / RAID1 / LVM CoW snapshot + ext3 / Debian 5.0 - lenny 2.6.26 kernel Tim Small
2010-09-17 22:59 ` Neil Brown
2010-09-20 19:59 ` Tim Small
2010-09-21 21:02 ` Tim Small
2010-09-21 22:30 ` Neil Brown [this message]
2010-10-12 13:59 ` Tim Small
2010-10-12 14:06 ` Tim Small
2010-10-12 16:48 ` CoolCold
2010-10-13 8:51 ` Tim Small
2010-10-13 13:00 ` CoolCold
2010-10-18 18:52 ` Tim Small
2010-10-19 6:16 ` Neil Brown
2010-10-19 16:24 ` Tim Small
2010-10-19 16:29 ` Tim Small
2010-10-19 19:29 ` Tim Small
2010-10-20 20:34 ` Tim Small
2010-10-20 23:04 ` Neil Brown
2010-11-18 18:04 ` Tim Small
2010-11-21 23:05 ` Neil Brown
2010-12-06 15:42 ` Tim Small
2010-09-21 22:21 ` Neil Brown
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=20100922083039.283ccdfd@notabene \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=tim@seoss.co.uk \
/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).