Dear all,
I create an RBD to be used as iSCSI target, with size close to the most
popular 3TB HDD size, 5860533168 512-byte sectors, or 715398*4M Ceph
objects (2.7 TB or 2794.4 GB). Then I add it into gwcli/disks (having to
specify the same size, 2861592M), and then, after some manipulations
which I do not remember exactly (like, remove it from gwcli conf, use it
for some time as RBD target in QEMU VM, then re-add it back to
gwcli/disks), I discover that its size is rounded up to 3 TiB, i.e. 3072
GiB or 786432*4M Ceph objects. As we know, GPT is stored at the end of
block device, so when we increase its size in this way, GPT becomes
inaccessible and partition limits need to be guessed anew in some other way.
I can shrink this gratuitously-increased RBD by 'rbd resize', and this
is reflected in 'gwcli ls /' (3.0T becomes 2.7T). But not in 'targetcli
ls /' (there, it is still 3.0T). Also, when I restart
rbd-target-gw.service, it gets resized back up to 3.0T as shown by
'gwcli ls /' and to 786432 objects in 'rbd info'. I look into
rbd/gateway.conf RADOS object, and don't see any explicit size specified
there. Where does it take this 3.0T size from ? My last suspicion is RBD
name which is 'tower-prime-e-3tb'. Can its '3tb' suffix be the culprit ?
Thank you in advance for your replies.
I am getting lost and slowly infuriated with this behavior.
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
