[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1696180] Re: Issues with qemu-img, libgfapi, and encryption at rest
From: |
Thomas Huth |
Subject: |
[Bug 1696180] Re: Issues with qemu-img, libgfapi, and encryption at rest |
Date: |
Wed, 05 May 2021 08:17:50 -0000 |
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/145
** Changed in: qemu
Status: Triaged => Expired
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #145
https://gitlab.com/qemu-project/qemu/-/issues/145
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1696180
Title:
Issues with qemu-img, libgfapi, and encryption at rest
Status in QEMU:
Expired
Bug description:
Hi,
Encryption-at-rest has been supported for some time now. The client
is responsible for encrypting the files with a help of a master key
file. I have a properly setup environment and everything appears to
be working fine but when I use qemu-img to move a file to gluster I
get the following:
# qemu-img convert -f raw -O raw linux.iso gluster://gluster01/virt0/linux.raw
[2017-06-06 16:52:25.489720] E [mem-pool.c:579:mem_put]
(-->/lib64/libglusterfs.so.0(syncop_lookup+0x4e5) [0x7f30f7a36d35]
-->/lib64/libglusterfs.so.0(+0x59f02) [0x7f30f7a32f02]
-->/lib64/libglusterfs.so.0(mem_put+0x190) [0x7f30f7a24a60] ) 0-mem-pool:
mem-pool ptr is NULL
[2017-06-06 16:52:25.490778] E [mem-pool.c:579:mem_put]
(-->/lib64/libglusterfs.so.0(syncop_lookup+0x4e5) [0x7f30f7a36d35]
-->/lib64/libglusterfs.so.0(+0x59f02) [0x7f30f7a32f02]
-->/lib64/libglusterfs.so.0(mem_put+0x190) [0x7f30f7a24a60] ) 0-mem-pool:
mem-pool ptr is NULL
[2017-06-06 16:52:25.492263] E [mem-pool.c:579:mem_put]
(-->/lib64/libglusterfs.so.0(syncop_lookup+0x4e5) [0x7f30f7a36d35]
-->/lib64/libglusterfs.so.0(+0x59f02) [0x7f30f7a32f02]
-->/lib64/libglusterfs.so.0(mem_put+0x190) [0x7f30f7a24a60] ) 0-mem-pool:
mem-pool ptr is NULL
[2017-06-06 16:52:25.497226] E [mem-pool.c:579:mem_put]
(-->/lib64/libglusterfs.so.0(syncop_create+0x44d) [0x7f30f7a3cf5d]
-->/lib64/libglusterfs.so.0(+0x59f02) [0x7f30f7a32f02]
-->/lib64/libglusterfs.so.0(mem_put+0x190) [0x7f30f7a24a60] ) 0-mem-pool:
mem-pool ptr is NULL
On and on until I get this message:
[2017-06-06 17:00:03.467361] E [MSGID: 108006] [afr-common.c:4409:afr_notify]
0-virt0-replicate-0: All subvolumes are down. Going offline until atleast one
of them comes back up.
[2017-06-06 17:00:03.467442] E [MSGID: 108006] [afr-common.c:4409:afr_notify]
0-virt0-replicate-1: All subvolumes are down. Going offline until atleast one
of them comes back up.
I asked for help assuming it's a problem with glusterfs and was told
it appears qemu-img's implementation of libgfapi doesn't call the
xlator function correctly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1696180/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug 1696180] Re: Issues with qemu-img, libgfapi, and encryption at rest,
Thomas Huth <=