From: starlight@binnacle.cx
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] cmp of inactive mirrored LV fails
Date: Fri, 02 Dec 2011 22:44:28 -0500 [thread overview]
Message-ID: <6.2.5.6.2.20111202223618.0399e7a0@binnacle.cx> (raw)
In-Reply-To: <6.2.5.6.2.20111202164221.063eb6d0@binnacle.cx>
On 12/02/2011 17:47 PM, Ron Johnson wrote:
>On 12/02/2011 03:47 PM, starlight binnacle cx wrote:
>
>It just occurred to me that the system
>in question is a development box that
>is abused in stress testing and other
>scenarios. It crashes in horrible ways
>fairly often.
>
>Unless you're testing the kernel or libc, crashes aren't really
>supposed to happen, even when putting the system under heavy
>load.
>
:-D !!!!!! Your joking right?
I know at least half a dozen ways to crash
or deadlock linux. Perhaps some of the
bugs have been fixed in newer kernels
(I generally report them), but like any
OS out there Linux has it holes. The
LVM bug where a system can be hung with
a mirrored swap LV is just one. Reported
it for RHEL 4 but I'll bet it's still
in there (it was obvious that RH had no
intention of fixing it).
https://bugzilla.redhat.com/show_bug.cgi?id=559959
next prev parent reply other threads:[~2011-12-03 3:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 17:20 [linux-lvm] cmp of inactive mirrored LV fails starlight
2011-12-02 18:34 ` starlight
2011-12-02 21:01 ` Stuart D. Gathman
2011-12-02 21:14 ` starlight
2011-12-02 21:54 ` Stuart D. Gathman
2011-12-02 22:02 ` starlight
2011-12-02 21:27 ` starlight
2011-12-02 21:47 ` starlight
2011-12-02 23:57 ` Ron Johnson
2011-12-03 3:44 ` starlight [this message]
2012-01-02 13:38 ` Lars Ellenberg
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=6.2.5.6.2.20111202223618.0399e7a0@binnacle.cx \
--to=starlight@binnacle.cx \
--cc=linux-lvm@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 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).