linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Robin Bowes <robin-lists@robinbowes.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Re: Snapshot segfaults lvremove + bug kernel
Date: Mon, 08 May 2006 23:19:04 +0100	[thread overview]
Message-ID: <445FC3D8.3000406@robinbowes.com> (raw)
In-Reply-To: <01b701c66dcb$5176d9d0$0101000a@jack>

Gabriel Barazer wrote:
> > Hello,
> >
> > I recently posted a LVM freeze while deleting snapshot, which could
> > be workaround-ed by issuing a dmsetup resume command.
> >
> > I was replied on the list that my tools weren't up to date (i had the
> > stable versions, the up to date are devel), so I retried the whole
> > thing (adding/deleting snapshot) with the new tools
> >
> > Versions are :
> > Kernel 2.6.16.1
> > LVM 2.02.05
> > Livdevmapper 1.02.05
> > Driver 4.5.0
> >
> > The lvcreate has been successfully created , but the lvremove after
> > gave me a segfault. Then the whole LVM system froze. After
> > hard-rebooting, the snapshot is still here. Anyone got the same , or
> > found a solution ?

I'm seeing a similar thing.

I've just started using snapshots as part of my backup process. I create
a snapshot, mount it, and take the backup from the snapshot then umount
and lvremove the snapshot when the backup has finished.

This seemed to be working but the server hung and required rebooting.
Now when I try and use lvremove to remove the snapshots the server hangs.

This is the output of lvs:

  LV           VG         Attr   LSize   Origin  Snap%  Move Copy%
  lv_home      VolGroup00 owi-ao   5.00G
  lv_home.snap VolGroup00 swi-a- 512.00M lv_home   5.35
  lv_root      VolGroup00 owi-ao   1.00G
  lv_root.snap VolGroup00 swi-a- 512.00M lv_root   9.14
  lv_scratch   VolGroup00 -wi-ao  50.00G
  lv_swap_01   VolGroup00 -wi-ao   4.00G
  lv_usr       VolGroup00 owi-ao   5.00G
  lv_usr.snap  VolGroup00 swi-a- 512.00M lv_usr    5.86
  lv_var       VolGroup00 owi-ao  54.09G
  lv_var.snap  VolGroup00 swi-a- 512.00M lv_var   40.77

This is on an x86_64 Fedora Core 4 system:

  Kernel:          kernel-2.6.16-1.2096_FC4
  LVM version:     2.01.08 (2005-03-22)
  Library version: 1.01.02 (2005-05-17)
  Driver version:  4.5.0

Any idea what might be causing this?

Any idea how to clean up the system, i.e. remove the
snapshots?

R.

  reply	other threads:[~2006-05-08 22:19 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 ` Robin Bowes [this message]
2006-05-09  9:41 ` Heinz Mauelshagen
2006-05-09 18:15   ` Robin Bowes
2006-05-10 10:48     ` Heinz Mauelshagen
2006-05-10 11:10       ` Robin Bowes
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=445FC3D8.3000406@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 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).