From: Bruno Bonfils <bonfils@fimasys.fr>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Re: Kernel bug with snapshots
Date: Sun, 16 Jan 2005 11:30:29 +0100 [thread overview]
Message-ID: <87wtudbr96.fsf@mononoke.fimasys.fr> (raw)
In-Reply-To: 20050115132055.GA18967@hcsd.de
Stephan Austerm�hle <au@hcsd.de> writes:
> Hi,
> in the last days I played around with Kernel 2.6.9, LVM2, and multiple
> snapshots of the Logical Volume leading to some system freezes. The
> Volume Group is setup on top of a mirrored device (md). I decided to
> switch to kernel 2.6.11-rc1 with Device Mapper patches 2.6.10-udm1
> (without patch 29) and test again.
I had exactly the same bug with 2.6.10 + dm patch (without the first
ones and the 29th)
Create a 50G volume, a first 10G snapshot, a second one few hours
after. When i tried to lvremove the first snapshot, my kernel crash.
> The lvremove instruction terminated with
> Segmentation fault
--
Bruno Bonfils
Fimasys
prev parent reply other threads:[~2005-01-16 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 13:20 [linux-lvm] Kernel bug with snapshots Stephan Austermühle
2005-01-16 10:30 ` Bruno Bonfils [this message]
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=87wtudbr96.fsf@mononoke.fimasys.fr \
--to=bonfils@fimasys.fr \
--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