From: Old Fart <rascal.jumper-747@cox.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] more info on the hang with 2.6.15-rc5
Date: Thu, 22 Dec 2005 12:13:49 -0500 [thread overview]
Message-ID: <43AADECD.7010106@cox.net> (raw)
In-Reply-To: <E1EpIfb-0001e2-GR@highlab.com>
Sebastian Kuzminsky wrote:
> 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.
>
>
>
This won't be much help, but, there are some indications of a kernel
problem with raid. The problems may be fedora specific, but, currently
fedora rawhide is following the upstream kernel. See:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=176179
good luck.
--
Regards,
Old Fart
next prev parent reply other threads:[~2005-12-22 17:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 5:07 [linux-lvm] more info on the hang with 2.6.15-rc5 Sebastian Kuzminsky
2005-12-22 5:07 ` Sebastian Kuzminsky
2005-12-22 17:13 ` Old Fart [this message]
2006-01-08 18:20 ` [linux-lvm] " Bill Davidsen
2006-01-08 18:20 ` Bill Davidsen
2006-01-09 2:33 ` [linux-lvm] " Sebastian Kuzminsky
2006-01-09 2:33 ` Sebastian Kuzminsky
2006-01-09 16:24 ` [linux-lvm] " Matthew Gillen
2006-01-09 16:24 ` Matthew Gillen
2006-01-09 16:35 ` [linux-lvm] " Matt Darcy
2006-01-09 17:27 ` Yeechang Lee
2006-01-09 18:05 ` Sebastian Kuzminsky
2006-01-09 18:05 ` Sebastian Kuzminsky
2006-01-09 17:13 ` Sebastian Kuzminsky
2006-01-09 17:46 ` Mattias Wadenstein
2006-01-09 9:54 ` Matt Darcy
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=43AADECD.7010106@cox.net \
--to=rascal.jumper-747@cox.net \
--cc=linux-lvm@redhat.com \
--cc=rascal.jumper-747@cox.net.spamorama.redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.