From: Leeman Strout <me@mooluv.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] lvm Bug? - bad reaction to snapshot creation
Date: Fri, 06 Jun 2014 19:26:26 -0400 [thread overview]
Message-ID: <53924E22.60403@mooluv.com> (raw)
Creating a snapshot throws an error "Attempted to decrement suspended
device counter below zero." but succeeds. Removing the snapshot fails,
attempting a 2nd time succeeds. Somewhere in this process the original
LV gets locked and the system needs to be restarted to unlock it. As
explained below this happens intermittently but regularly.
Any additional info please let me know directly, I am not a subscriber,
Leeman
----
log file: http://www.enlj.com/lvm.txt
lvm config: http://www.enlj.com/lvmconfig.txt
Arch Linux, lvm2 2.02.106-2
line 1: lvcreate -L1G -s -n srvrootsnap /dev/ssd.vg/server-root
Attempted to decrement suspended device counter below zero.
Logical volume "srvrootsnap" created
line 148+: why? globalfilter = [ "a|/dev/md|", "r|.*|" ]
line 921: after this point I do udevadm settle
no output from udevadm settle
line 923: lvremove -f /dev/ssd.vg/srvrootsnap - fails
Unable to deactivate open ssd.vg-srvrootsnap-cow (253:3)
Failed to activate srvrootsnap.
Releasing activation in critical section.
libdevmapper exiting with 1 device(s) still suspended.
line 1567: lvremove -f /dev/ssd.vg/srvrootsnap - again, works this time
Logical volume "srvrootsnap" successfully removed
However, /dev/ssd.vg/server-root is locked up, the VM seizes as no data
can be written to the volume. I have to restart the entire system to
unlock the volume.
This doesn't happen all the time. It happens every time I do a backup.
1 of the 7 LV snapshots created for the job, not always the same one.
hardware: Supermicro X9DR3-F,
onboard SATA controller:
00:1f.2 SATA controller: Intel Corporation C600/X79 series chipset
6-Port SATA AHCI Controller (rev 06)
/dev/md0 consists of 2 Seagate 600 240GB SSDs on that controller
/dev/ssd.vg consists of /dev/md0
next reply other threads:[~2014-06-06 23:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 23:26 Leeman Strout [this message]
2014-06-09 9:50 ` [linux-lvm] lvm Bug? - bad reaction to snapshot creation Zdenek Kabelac
2014-06-09 10:08 ` Marian Csontos
2014-06-09 14:55 ` Leeman Strout
2014-06-09 14:53 ` Leeman Strout
2014-06-10 7:58 ` Zdenek Kabelac
2014-06-10 13:45 ` Leeman Strout
2014-06-10 15:22 ` Leeman Strout
2014-06-11 7:59 ` Christian Hesse
2014-06-10 8:31 ` Zdenek Kabelac
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=53924E22.60403@mooluv.com \
--to=me@mooluv.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).