From: Sebastian Kuzminsky <seb@highlab.com>
To: linux-raid@vger.kernel.org, linux-lvm@redhat.com
Subject: [linux-lvm] more info on the hang with 2.6.15-rc5
Date: Wed, 21 Dec 2005 22:07:15 -0700 [thread overview]
Message-ID: <E1EpIfb-0001e2-GR@highlab.com> (raw)
Now it works, but I dont trust it one bit.
I had been seeing almost immediate, perfectly repeatable hard lockups
in 2.6.15-rc5 and 2.6.15-rc5-mm3, when using sata_mv, RAID, and LVM
together. Nothing in the syslog or on the console, and the system is
totally unresponsive to the keyboard & network.
My hardware setup is: four Seagate Barracuda 500 GB disks, on a Marvell
MV88SX6081 8-port SATA-II PCI-X controller, on a PCI-X bus (64/66).
The disks work great when accessed directly. They work great when used
as four PVs for LVM, and when assembled into a 4-disk RAID-6.
But when I make a RAID-6 array out of them, and use the array as a PV,
the system would hang completely, within seconds. (This is with LVM
2.02.01, libdevicemapper 1.02.02, and dm-driver 4.5.0.)
I turned on all the debugging options in the kernel config hoping to get
some insight, but this "debug" kernel doesnt crash. It's running fine,
and I'm pounding on it. A timing problem in the interaction between
LVM and RAID? Some kind of wierd heisenbug....
I'd be happy to do any debugging tests people suggest.
--
Sebastian Kuzminsky
next reply other threads:[~2005-12-22 5:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 5:07 Sebastian Kuzminsky [this message]
2005-12-22 17:13 ` [linux-lvm] more info on the hang with 2.6.15-rc5 Old Fart
2006-01-08 18:20 ` [linux-lvm] " Bill Davidsen
2006-01-09 2:33 ` Sebastian Kuzminsky
2006-01-09 16:24 ` Matthew Gillen
2006-01-09 17:13 ` Sebastian Kuzminsky
[not found] ` <43C290D4.5030209@projecthugo.co.uk>
[not found] ` <17346.40174.865171.160466@dobie.ylee.org>
2006-01-09 18:05 ` Sebastian Kuzminsky
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=E1EpIfb-0001e2-GR@highlab.com \
--to=seb@highlab.com \
--cc=linux-lvm@redhat.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).