linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Christopher Hawkins <chawkins@bplinux.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] kernel panic on lvcreate
Date: Thu, 10 Dec 2009 10:04:40 -0500 (EST)	[thread overview]
Message-ID: <8023092.631260457480892.JavaMail.javamailuser@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0912100949260.8205@bmsred.bmsi.com>

It is reported here:

https://bugzilla.redhat.com/show_bug.cgi?id=539328

That is definitely the one. And it sounds like they have a potential fix... I have already emailed the developers there asking if I can help test their patch, so hopefully soon I can post back and report status. 

Christopher Hawkins

----- "Stuart D. Gathman" <stuart@bmsi.com> wrote:

> On Wed, 9 Dec 2009, Christopher Hawkins wrote:
> 
> > After some time I revisited this issue on a freshly installed Centos
> 5.4 box,
> > latest kernel (2.6.18-164.6.1.el5 ) and the panic is still
> reproducible. Any
> > time I create a snapshot of the root filesystem, kernel panics. The
> LVM HOWTO
> > says to post bug reports to this list. Is this the proper place?
> 
> Bummer.  I would post the bug on Centos bugzilla also.  Please post
> the
> bug number here if you do it (cause I'll get to it eventually).
> 
> Thanks for testing this.  I have the same problem, and have a new
> client
> to install by next year - so not much time to work on it.
> 
> Now that we know it is not yet fixed, we can form theories as to what
> is going wrong.  My guess is that the problem is caused by the fact
> that
> lvm is updating files in /etc/lvm on the root filesystem while taking
> the snapshot.  These updates are done by user space programs, so I
> would
> further speculate that *any* snapshot would crash if an update
> happened exactly
> when creating the snapshot - i.e. the atomic nature of snapshot
> creation has
> been broken.  The lvm user space probably does fsync() on files
> in /etc/lvm, which might be involved in triggering the crash.
> 
> We could test the first theory by moving /etc/lvm to another volume
> (I
> sometimes put it on /boot - a non LVM filesystem - for easier
> disaster
> recovery.) Naturally, I wouldn't go moving /etc/lvm on a production
> server.
> 
> Testing the second hypothesis is less certain, and would basically
> involve
> trying snapshots of LVs undergoing heavy updating.
> 
> -- 
> 	      Stuart D. Gathman <stuart@bmsi.com>
>     Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703
> 591-6154
> "Confutatis maledictis, flammis acribus addictis" - background song
> for
> a Microsoft sponsored "Where do you want to go from here?"
> commercial.
> 
> _______________________________________________
> 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/

  reply	other threads:[~2009-12-10 15:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <33462681.271260370580061.JavaMail.javamailuser@localhost>
2009-12-09 15:00 ` [linux-lvm] kernel panic on lvcreate Christopher Hawkins
2009-12-09 20:18   ` Milan Broz
2009-12-10 15:08     ` Stuart D. Gathman
2009-12-10 15:00   ` Stuart D. Gathman
2009-12-10 15:04     ` Christopher Hawkins [this message]
2009-12-11 14:23       ` Christopher Hawkins
     [not found] <6113890.251257449494023.JavaMail.javamailuser@localhost>
2009-11-05 19:38 ` Christopher Hawkins
2009-11-06 13:22   ` Christopher Hawkins
     [not found] <30507140.01257271012362.JavaMail.javamailuser@localhost>
2009-11-03 18:00 ` Christopher Hawkins
2009-11-03 18:58   ` Christopher Hawkins
2009-11-04 18:58   ` Stuart D. Gathman
2009-11-05 19:30     ` Stuart D. Gathman
     [not found] <21080952.761257260436402.JavaMail.javamailuser@localhost>
2009-11-03 15:07 ` Christopher Hawkins
2009-11-03 17:07   ` Milan Broz

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=8023092.631260457480892.JavaMail.javamailuser@localhost \
    --to=chawkins@bplinux.com \
    --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).