how to remove big ISCSI disk
Pages: 1 2
admin
2,930 Posts
June 29, 2019, 12:56 pmQuote from admin on June 29, 2019, 12:56 pmHi
Can you show all the cli commands you had done or they are all in your first post ? in the first post you referenced 2 different uuids, i just want to make sure there are no other commands.
if you are sure the problem exists on this disk only and new ones can be attached OK + you have production data + not too much data, then we can copy the disk to a new disk using rbd export / rbd import or rbd copy then attach the new disk.
what version of PetaSAN are you using ?
Hi
Can you show all the cli commands you had done or they are all in your first post ? in the first post you referenced 2 different uuids, i just want to make sure there are no other commands.
if you are sure the problem exists on this disk only and new ones can be attached OK + you have production data + not too much data, then we can copy the disk to a new disk using rbd export / rbd import or rbd copy then attach the new disk.
what version of PetaSAN are you using ?
elwan
14 Posts
July 1, 2019, 2:59 pmQuote from elwan on July 1, 2019, 2:59 pmcommande i have done is related to my first post.I used this method two time with good result at the third time i got this issue.
Disk content many datas more than 20TB.
i use petasan 2.2.
Thanks.
commande i have done is related to my first post.I used this method two time with good result at the third time i got this issue.
Disk content many datas more than 20TB.
i use petasan 2.2.
Thanks.
admin
2,930 Posts
July 1, 2019, 4:28 pmQuote from admin on July 1, 2019, 4:28 pmThe copy is the most straightforward fix if you can tolerate the time.
I want to know the exact commands you used, ie with all the parameters (including image uuid numbers) . You can also send me the /opt/petasan/log/PetaSAN.log file to contact-us at petasan.org
If you upgrade to 2.3, it does have cli scripts to read/write metadata and attach/detach manually, so this may help.
Ultimately it is possible to create a new image and instead of copying data to it, it is possible to modify its uuid to point to the problem image, but you need to know what you are doing.
The copy is the most straightforward fix if you can tolerate the time.
I want to know the exact commands you used, ie with all the parameters (including image uuid numbers) . You can also send me the /opt/petasan/log/PetaSAN.log file to contact-us at petasan.org
If you upgrade to 2.3, it does have cli scripts to read/write metadata and attach/detach manually, so this may help.
Ultimately it is possible to create a new image and instead of copying data to it, it is possible to modify its uuid to point to the problem image, but you need to know what you are doing.
elwan
14 Posts
July 1, 2019, 5:47 pmQuote from elwan on July 1, 2019, 5:47 pmi send an email with detail as you demanded.
i am open for any solution.
i send an email with detail as you demanded.
i am open for any solution.
elwan
14 Posts
July 4, 2019, 10:01 amQuote from elwan on July 4, 2019, 10:01 amThanks for your support it's resolved.Just upgrade 2.2 to 2.3.
Thanks for your support it's resolved.Just upgrade 2.2 to 2.3.
Pages: 1 2
how to remove big ISCSI disk
admin
2,930 Posts
Quote from admin on June 29, 2019, 12:56 pmHi
Can you show all the cli commands you had done or they are all in your first post ? in the first post you referenced 2 different uuids, i just want to make sure there are no other commands.
if you are sure the problem exists on this disk only and new ones can be attached OK + you have production data + not too much data, then we can copy the disk to a new disk using rbd export / rbd import or rbd copy then attach the new disk.
what version of PetaSAN are you using ?
Hi
Can you show all the cli commands you had done or they are all in your first post ? in the first post you referenced 2 different uuids, i just want to make sure there are no other commands.
if you are sure the problem exists on this disk only and new ones can be attached OK + you have production data + not too much data, then we can copy the disk to a new disk using rbd export / rbd import or rbd copy then attach the new disk.
what version of PetaSAN are you using ?
elwan
14 Posts
Quote from elwan on July 1, 2019, 2:59 pmcommande i have done is related to my first post.I used this method two time with good result at the third time i got this issue.
Disk content many datas more than 20TB.
i use petasan 2.2.
Thanks.
commande i have done is related to my first post.I used this method two time with good result at the third time i got this issue.
Disk content many datas more than 20TB.
i use petasan 2.2.
Thanks.
admin
2,930 Posts
Quote from admin on July 1, 2019, 4:28 pmThe copy is the most straightforward fix if you can tolerate the time.
I want to know the exact commands you used, ie with all the parameters (including image uuid numbers) . You can also send me the /opt/petasan/log/PetaSAN.log file to contact-us at petasan.org
If you upgrade to 2.3, it does have cli scripts to read/write metadata and attach/detach manually, so this may help.
Ultimately it is possible to create a new image and instead of copying data to it, it is possible to modify its uuid to point to the problem image, but you need to know what you are doing.
The copy is the most straightforward fix if you can tolerate the time.
I want to know the exact commands you used, ie with all the parameters (including image uuid numbers) . You can also send me the /opt/petasan/log/PetaSAN.log file to contact-us at petasan.org
If you upgrade to 2.3, it does have cli scripts to read/write metadata and attach/detach manually, so this may help.
Ultimately it is possible to create a new image and instead of copying data to it, it is possible to modify its uuid to point to the problem image, but you need to know what you are doing.
elwan
14 Posts
Quote from elwan on July 1, 2019, 5:47 pmi send an email with detail as you demanded.
i am open for any solution.
i send an email with detail as you demanded.
i am open for any solution.
elwan
14 Posts
Quote from elwan on July 4, 2019, 10:01 amThanks for your support it's resolved.Just upgrade 2.2 to 2.3.
Thanks for your support it's resolved.Just upgrade 2.2 to 2.3.