On 11/21/2012 04:50 AM, Andrey Korolyov wrote:
Hi,
Somehow I have managed to produce unkillable snapshot, which does not
allow to remove itself or parent image:
$ rbd snap purge dev-rack0/vm2
Removing all snapshots: 100% complete...done.
I see one bug with 'snap purge' ignoring the return code when removing
snaps. I just fixed this in the next branch. It's probably getting the
same error as 'rbd snap rm' below.
Could you post the output of:
rbd snap purge dev-rack0/vm2 --debug-ms 1 --debug-rbd 20
$ rbd rm dev-rack0/vm2
2012-11-21 16:31:24.184626 7f7e0d172780 -1 librbd: image has snapshots
- not removing
Removing image: 0% complete...failed.
rbd: image has snapshots - these must be deleted with 'rbd snap purge'
before the image can be removed.
$ rbd snap ls dev-rack0/vm2
SNAPID NAME SIZE
188 vm2.snap-yxf 16384 MB
$ rbd info dev-rack0/vm2
rbd image 'vm2':
size 16384 MB in 4096 objects
order 22 (4096 KB objects)
block_name_prefix: rbd_data.1fa164c960874
format: 2
features: layering
$ rbd snap rm --snap vm2.snap-yxf dev-rack0/vm2
rbd: failed to remove snapshot: (2) No such file or directory
$ rbd snap create --snap vm2.snap-yxf dev-rack0/vm2
rbd: failed to create snapshot: (17) File exists
$ rbd snap rollback --snap vm2.snap-yxf dev-rack0/vm2
Rolling back to snapshot: 100% complete...done.
$ rbd snap protect --snap vm2.snap-yxf dev-rack0/vm2
$ rbd snap unprotect --snap vm2.snap-yxf dev-rack0/vm2
Meanwhile, ``rbd ls -l dev-rack0'' segfaulting with an attached log.
Is there any reliable way to kill problematic snap?
From this log it looks like vm2 used to be a clone, and the snapshot
vm2.snap-yxf was taken before it was flattened. Later, the parent of
vm2.snap-yxf was deleted. Is this correct?
It was a bug in 0.53 that protected snapshots could be deleted.
Josh
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
