Package: libmagic1
Version: 5.11-2
An example tells it best:
# ls -l disk
-rw-r--r-- 1 libvirt-qemu kvm 639631360 Oct 1 01:28 disk
# file disk
disk: QEMU QCOW Image (v2), has backing file (path
/var/lib/nova/instances/_base/a76b0c55d810618947089ee2e41f396a6), 10737418240
bytes
# ls -l /var/lib/nova/instances/_base/a76b0c55d810618947089ee2e41f396a6
ls: cannot access
/var/lib/nova/instances/_base/a76b0c55d810618947089ee2e41f396a6: No such file
or directory
# ls -l /var/lib/nova/instances/_base/a76b0c55d810618947089ee2e41f396a6*
-rw-rw-r-- 1 nova nova 10737418240 Oct 1 01:32
/var/lib/nova/instances/_base/a76b0c55d810618947089ee2e41f396a64fbfc10
-rw-rw-r-- 1 nova kvm 10737418240 Oct 1 01:32
/var/lib/nova/instances/_base/a76b0c55d810618947089ee2e41f396a64fbfc10_10
Note how the final 7 ('4fbfc10') or 10 ('4fbfc10_10') characters have
been truncated from the filename. I have no way of telling which one of
those two files are the actual backing file for this qcow2 image.
This makes it impossible to extract the backing filename (e.g. by piping
file's output into awk or something) for use in a script.
It is particularly problematic for qemu-nbd which depends on libmagic1
to be able to create a network block device for the qcow2 image (e.g. so
that any of the disk/partition level tools like fsck and mount can be
run against the qcow2 image).
craig
--
craig sanders <c...@taz.net.au>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
