decompiled crushmap device list after removing osd

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

 



Hi,
I noticed some weird behaviour of crushtool when decompiling a map after an osd has been removed. Say I have a cluster with 4 osds. When I remove osd.2, get and decompile the crushmap, I get this device list in the crushmap:

# devices
device 0 osd.0 class hdd
device 1 osd.1 class hdd
device 2 device2
device 3 osd.3 class hdd

I'd appreciate some info on whether this is intended behaviour and what the reasoning is. I'd expect the map not to list id 2 at all and afaict the crushmap doesn't contain the id anymore. If there is no reason for listing that I'd be happy to make a PR.

Best,
Jan

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux