All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Bowes <robin-lists@robinbowes.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Snapshot segfaults lvremove + bug kernel
Date: Wed, 10 May 2006 12:10:24 +0100	[thread overview]
Message-ID: <4461CA20.2050305@robinbowes.com> (raw)
In-Reply-To: <20060510104844.GR31579@redhat.com>

Heinz Mauelshagen wrote:
> On Tue, May 09, 2006 at 07:15:25PM +0100, Robin Bowes wrote:
>> Do you have any idea when we might see a fix for this? Is the bug
>> present in later versions?
> 
> A fix has been provided ~2 weeks ago to lkml and was tested ok.
> It is in the recent stable kernels.

Can you define "recent" so I know which to install.

>> For example, I've got a box running FC4 that has this problem. If I
>> upgrade to FC5 am I likely to still see the problem?
> 
> Yes.

So, the FC5 kernels don't have the fix? Even in the Testing repos?

>> Also, what's the best way to get rid of the snapshot volumes? I'm
>> currently planning to boot from a recovery disk that supports lvm and
>> run lvremove from there.
> 
> That or using a n actual stable kernel *should* work,
> because tearing down kcopyd jobs dies with the bug under load.

OK, thanks.

R.

  reply	other threads:[~2006-05-10 11:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-02  9:32 [linux-lvm] Snapshot segfaults lvremove + bug kernel Gabriel Barazer
2006-05-08 22:19 ` [linux-lvm] " Robin Bowes
2006-05-09  9:41 ` [linux-lvm] " Heinz Mauelshagen
2006-05-09 18:15   ` Robin Bowes
2006-05-10 10:48     ` Heinz Mauelshagen
2006-05-10 11:10       ` Robin Bowes [this message]
2006-05-13  0:07         ` [linux-lvm] " Robin Bowes
2006-05-18 22:44       ` Robin Bowes

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=4461CA20.2050305@robinbowes.com \
    --to=robin-lists@robinbowes.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 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.