From: Matthew Gillen <me@mattgillen.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Re: more info on the hang with 2.6.15-rc5
Date: Mon, 09 Jan 2006 11:24:50 -0500 [thread overview]
Message-ID: <43C28E52.8080104@mattgillen.net> (raw)
In-Reply-To: <E1Evmqw-0001pO-Ng@highlab.com>
Sebastian Kuzminsky wrote:
> Bill Davidsen <davidsen@tmr.com> wrote:
>
>>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.
>>>
>>>
>>>
>>>
>>
>>I've been waiting for more info on this, did it get fixed? 2.6.15?
>
>
> Still broken in 2.6.15. With all the debugging options OFF in the config,
> the system stayed up < 24 hours under load, then a hard lockup like
> before: nothing on the console, magic sysrq doesnt work, no caps-lock,
> no ping. Note that this is different from before: it actually ran a
> little bit before locking up, rather than locking up within seconds like
> it did with 2.6.15-rc5.
>
> With all the debugging options ON, it's stayed up for 3+ days now (and
> still running) with no problems.
>
>
> Any suggestions for how to debug this are welcome! ;-)
I couldn't quite tell from your description: are you getting the lockup
when you try to mount a filesystem that uses the RAID+LVM as a device?
Or do you get errors when doing LVM-level stuff (ie no filesystem can
even be put on the device)?
In the case of the former, what filesystem are you using?
--Matt
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2006-01-09 16:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 5:07 more info on the hang with 2.6.15-rc5 Sebastian Kuzminsky
2006-01-08 18:20 ` Bill Davidsen
2006-01-09 2:33 ` Sebastian Kuzminsky
2006-01-09 16:24 ` Matthew Gillen [this message]
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 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=43C28E52.8080104@mattgillen.net \
--to=me@mattgillen.net \
--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).