Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

Strange thing happened when creating new iSCSI disk

Hi everyone,

For some reasons I got a strange issue when adding new iSCSI disk, which changed my old iSCSI disks into the new name  to the newly added and therefore cut off any control into the old disks.

I've attached you a picture showing the issue. The previous disk is with ID 00016, basically the newly added would be ID 00017, but it also changes 00015 to 00017, leading the system got 2 disks with same ID.

I think it is some problems with the counter but do not know how to reset it. May you help me to fix it out?

Image => https://drive.google.com/file/d/1uNixoKhrbGp4ScqQSn-COq5mRkxuGdzy/view

 

Hi,

can you show the output of

grep "rbd info"  /usr/lib/python2.7/dist-packages/PetaSAN/core/ceph/api.py

Hi, thanks for response

I'm really sorry that due to the need of my company, I have to fresh install the whole system within 4 hours using the previous stable 2.2.0 version.

I will do the same steps at last time on the QR system and if the problem persists, I will give you the output.

Regards,
Tom

most likely you hit a bug in ec pools we found just after releasing 2.3, it was fixed re-uploaded very early on. i would recommend you re-download version 2.3 and use this.

Hi,

As expected, I got the same issue again (and yes, on EC).

I've attached you the output (in italic) as below.

root@petasan-node01:~# grep "rbd info" /usr/lib/python2.7/dist-packages/PetaSAN/core/ceph/api.py
cmd = "rbd info " + pool + "/" + str(image) + " " + ceph_auth.get_authentication_string() + " --cluster " + cluster_name + " | grep rbd_data | cut -d \'.\' -f 2"

Quote from admin on August 2, 2019, 8:45 am

most likely you hit a bug in ec pools we found just after releasing 2.3, it was fixed re-uploaded very early on. i would recommend you re-download version 2.3 and use this.

The newly-download file checksum and my ISO for 2.3 installer one are the same, so I think the bug persisted on my case?

i would recommend using 2.3 for the new install.

The grep you show does show the bug.  this was fixed very early on, make sure you download and install the recent version.