From: PGNet Dev <pgnet.dev@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] errors on lvcreate snapshot : "device-mapper: remove ioctl on (...) failed: Device or resource busy"; still unresolved old issue, or new?
Date: Sun, 29 Nov 2015 15:10:09 -0800 [thread overview]
Message-ID: <565B85D1.1080901@gmail.com> (raw)
I run
lvs --version
LVM version: 2.02.120(2) (2015-05-15)
Library version: 1.03.01 (2015-05-15)
Driver version: 4.33.0
on OpenSUSE Leap
lsb_release -rd
Description: openSUSE Leap 42.1 (x86_64)
Release: 42.1
Exec of LV snapshots of active LVs reports ERRORs
lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log
Cpy%Sync Convert
LV01 VG0 -wi-ao---- 352.00m
LV02 VG0 -wi-ao---- 5.00g
LV03 VG0 -wi-ao---- 512.00m
lvcreate -L 352M -s -n SNAP01 /dev/VG0/LV01
device-mapper: remove ioctl on (254:3) failed: Device or resource busy
Logical volume "SNAP01" created.
lvcreate -L 512M -s -n SNAP03 /dev/VG0/LV03
device-mapper: remove ioctl on (254:15) failed: Device or resource busy
Logical volume "SNAP03" created.
lvcreate -L 5G -s -n SNAP02 /dev/VG0/LV02
device-mapper: remove ioctl on (254:18) failed: Device or resource busy
Logical volume "SNAP02" created.
similar to similar errors referenced in BUG
Bug 927437 - "device-mapper: remove ioctl on failed" error when
creating thin pool volume
https://bugzilla.redhat.com/show_bug.cgi?id=927437#c10
but still creates the snapshot LVs
lvs | grep SNAP
LV VG Attr LSize Pool Origin Data% Meta% Move
Log Cpy%Sync Convert
SNAP01 VG0 swi-a-s--- 352.00m LV01 0.00
SNAP02 VG0 swi-a-s--- 5.00g LV02 0.01
SNAP03 VG0 swi-a-s--- 512.00m LV03 0.00
Are the "device-mapper: remove ioctl on (254:18) failed" still the
same/similar issue as #927437, new upstream issue, or distro-specific?
reply other threads:[~2015-11-29 23:10 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=565B85D1.1080901@gmail.com \
--to=pgnet.dev@gmail.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.