Re: Remove rbd image after interrupt of deletion command

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 11 Jun 2019 at 14:46, Sakirnth Nagarasa
<sakirnth.nagarasa@xxxxxx> wrote:
> On 6/7/19 3:35 PM, Jason Dillaman wrote:
[...]
> > Can you run "rbd rm --log-to-stderr=true --debug-rbd=20
> > ${POOLNAME}/${IMAGE}" and provide the logs via pastebin.com?
> >
> >> Cheers,
> >> Sakirnth
>
> It is not necessary anymore the remove command worked. The problem was
> only "rbd info" command. It took approximately one day to remove the
> cloned image (50 TB) which was not flaten. Why it took so long? The
> clone command completed within seconds.
>
> Thanks,
> Sakirnth

Sakirnth,

previously you've said (statement A): "...
rbd rm ${POOLNAME}/${IMAGE}
rbd: error opening image ${IMAGE}: (2) No such file or directory
..."

Now you're saying (statement B): "rm worked and the only issue was
info command".
Obviously both statements can't be true at the same time.
Can you elaborate(?) on that matter so that  themail list users would
have better understanding.

-- 
End of message. Next message?
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux