From: "Tim Cary" <TDC@yesinc.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM Snapshot create trouble
Date: Mon, 06 Mar 2006 14:21:36 -0500 [thread overview]
Message-ID: <s40c4576.090@fs02.yesinc.com> (raw)
Hello,
This post relates to an issue posted by Steffen Plotner back in
December. See
https://www.redhat.com/archives/linux-lvm/2005-December/msg00105.html
I am experiencing the same type of problem.
On 2.6.13-1.1532_FC4:
When a lot of write activity is going on my server goes into a dead
lock trying to create a snapshot. The write activity is from creating
the snap itself, as disk i/o normally is not intense on this server.
lvm_snap_copy> source: /dev/vg_scsi_0/lv_os_root
lvm_snap_copy> target: /dev/vg_scsi_0/lv_os_root_alt
lvm_snap_create> source: /dev/vg_scsi_0/lv_os_root
lvm_snap_create> target: snap
lvm_snap_create> snap_space: 15%
lvm_snap_create> source uuid: Jm4sGV-fGt5-XRHl-ESds-AERY-pZtq-GOg8Tu
lvm_snap_create> short name: lv_os_root
lvm_snap_create> size: 8388608000 bytes
lvm_snap_create> snap_size: 1200 Mb
lvm_snap_create> lvcreate -s -L1200 -n lv_os_root_snap
/dev/vg_scsi_0/lv_os_root
Rounding up size to full physical extent 1.19 GB
At this point no I/O was possible. No ssh, no x terminal, no logging
into the console, nothing at all! Disk activity was null. In VNC you
could see the load window all black filled. I had to push the reset
button on the server.
This is on some very decent hardware- 3Ghz Xenon, 4Gb RAM, 7200RPM SCSI
Hardware raid controller drives.
When I run the same command on a different system, same hardware (but a
bit less loaded CPU wise), I did not yet have this problem, however I
have been able to reproduce this same type of issue, it seems when there
is continuous i/o, one can not remove the snapshot until all i/o
ceases.
Can anyone reproduce this problem? Now there are at least two of us
with the same exact issue.
Tim
reply other threads:[~2006-03-06 19:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=s40c4576.090@fs02.yesinc.com \
--to=tdc@yesinc.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.