Hi,
Thanks for this hint, seems it happens a lot with proxmox users, lists
are full of such issues. Happened to me today when cloning on a proxmox
server with connectivity issues and where the process hanged.
Maybe a hook could be provided for an easier fix.
Cheers,
Andrej
On 11/03/2021 10:
Thanks a lot, that fixed the problem.
For the record, we are running nautilus 14.2.11 and there is no such
'--input-file' option for setomapval.
`#rados -p volumes setomapval rbd_trash id_5afa5e5a07b8bc < key_file`
does the trick.
Cheers,
Enrico
On 10/03/2021 17:17, Jason Dillaman wrote:
O
Odd, it looks like it's stuck in the "MOVING" state. Perhaps the "rbd
trash mv" command was aborted mid-operation? The way to work around
this issue is as follows:
$ rados -p volumes getomapval rbd_trash id_5afa5e5a07b8bc key_file
$ hexedit key_file ## CHANGE LAST BYTE FROM '01' to '00'
$ rados -p
Hello Jason,
# rados -p volumes listomapvals rbd_trash
id_5afa5e5a07b8bc
value (71 bytes) :
02 01 41 00 00 00 00 2b 00 00 00 76 6f 6c 75 6d
|..A+...volum|
0010 65 2d 30 32 64 39 35 39 66 65 2d 61 36 39 33 2d
|e-02d959fe-a693-|
0020 34 61 63 62 2d 39 35 65 32 2d 63 61
Can you provide the output from "rados -p volumes listomapvals rbd_trash"?
On Wed, Mar 10, 2021 at 8:03 AM Enrico Bocchi wrote:
>
> Hello everyone,
>
> We have an unpurgeable image living in the trash of one of our clusters:
> # rbd --pool volumes trash ls
> 5afa5e5a07b8bc volume-02d959fe-a693-4a
