From: "Marcel Gsteiger" <Marcel.Gsteiger@milprog.ch>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Can't get rid of INACTIVE read/write snapshot
Date: Mon, 02 Jun 2008 18:27:19 +0200 [thread overview]
Message-ID: <48443B86.DB9C.0010.0@milprog.ch> (raw)
Hi all
I'm using lvm2-2.01.08-2.1 on fc4, kernel 2.6.16-1 with linux-vserver patches.
A while ago, I mistakenly created a 39GB read-write snapshot of my /vservers partition (which, btw, seemed to work). But after some time this partition got to an overflow and since then I can't get rid of it anymore. See the lvdisplay output below.
lvchange -an or --refresh gives me a message "Can't change snapshot logical volume "vservers_snapshot"".
lvremove lets me wait, then "top" shows 100% IO-Wait but does not come to an end (at least after an hour). I don't know how much patience I would need, this box is rather fast otherwise (dual xeon 2.8GHz w/ SATA drives).
Rebooting does not help anything.
Is there a safe way to simply get rid of this snapshot? Any help would much be appreciated.
Regards
--Marcel
--- Logical volume ---
LV Name /dev/vg00/lv00_vservers
VG Name vg00
LV UUID 9oELP3-2l7d-gTML-2xg2-unTu-znP0-qVd3Mc
LV Write Access read/write
LV snapshot status source of
/dev/vg00/vservers_snapshot [INACTIVE]
LV Status available
# open 1
LV Size 39,06 GB
Current LE 625
Segments 1
Allocation contiguous
Read ahead sectors 0
Block device 253:9
--- Logical volume ---
LV Name /dev/vg00/vservers_snapshot
VG Name vg00
LV UUID cQEj3z-V2jD-QOCl-3Yea-ETQZ-Egj9-2B7nd2
LV Write Access read/write
LV snapshot status INACTIVE destination for /dev/vg00/lv00_vservers
LV Status available
# open 0
LV Size 39,06 GB
Current LE 625
Segments 1
Snapshot chunk size 4,00 KB
Allocated to snapshot 100,00%
Allocation inherit
Read ahead sectors 0
Block device 253:8
next reply other threads:[~2008-06-02 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 16:27 Marcel Gsteiger [this message]
2008-06-03 19:15 ` [linux-lvm] Can't get rid of INACTIVE read/write snapshot Mikulas Patocka
2008-07-21 8:13 ` Antw: " Marcel Gsteiger
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=48443B86.DB9C.0010.0@milprog.ch \
--to=marcel.gsteiger@milprog.ch \
--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.