From: Tim Small <tim@seoss.co.uk>
To: CoolCold <coolthecold@gmail.com>
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, 13 Oct 2010 09:51:14 +0100 [thread overview]
Message-ID: <4CB57302.4080409@seoss.co.uk> (raw)
In-Reply-To: <AANLkTi=Ye_74791SUPOj0RhQ+qmHVNPDjHkv-ZdKLXBo@mail.gmail.com>
Hi,
On 12/10/10 17:48, CoolCold wrote:
> Just in case you don't know 2.6.26 branch is "frozen, not maintained"
> - http://wiki.openvz.org/Download/kernel/2.6.26/2.6.26-gogol.1
>
Yep, but that's by OpenVZ, I'm using the Debian kernel, and 2.6.26 is
Debian stable, and so supported by the Debian kernel team....
> The only stable for now is 2.6.18& 2.6.9 , any other is
> outdated/testing http://wiki.openvz.org/Download/kernel . Ongoin start
> is 2.6.32 as being new RHEL6 kernel. So i'd suggest you to go down to
> .18 or take .32 from backports.
>
Once RHEL6 and/or Debian6.0 has been out for a few months, I'll probably
switch to 2.6.32, but I don't feel sufficiently confident to do that yet
(not for OpenVZ boxes anyway - OpenVZ+2.6.32 just hasn't had enough
testing-time yet for production IMO) - I also look after plenty of
non-openvz 2.6.26 Debian 5.0 boxes, and if this bug is md+lvm+ext3
(which in my semi-educated opinion looks most likely, partly because
there have been some similar looking deadlocks reported on non-OpenVZ
Debian 5.0 systems), then it'd be preferable to track-down the cause of
this and get it fixed....
Cheers,
Tim.
--
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309
next prev parent reply other threads:[~2010-10-13 8:51 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
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 [this message]
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=4CB57302.4080409@seoss.co.uk \
--to=tim@seoss.co.uk \
--cc=coolthecold@gmail.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).