Missing journal information of new OSD after disk replacement
atselitan
21 Posts
May 22, 2020, 12:20 pmQuote from atselitan on May 22, 2020, 12:20 pmHello
I have PetaSAN cluster upgraded to 2.5.1 version (cluster is more then two years old)
After broken disk replace and add new storage device, there is no information displayed about a journal of new storage device in WEB.
But using ssh console i can see information about existing journal (block.db) on nvme disk:
Is that alright or a bug?
Hello
I have PetaSAN cluster upgraded to 2.5.1 version (cluster is more then two years old)
After broken disk replace and add new storage device, there is no information displayed about a journal of new storage device in WEB.
But using ssh console i can see information about existing journal (block.db) on nvme disk:
Is that alright or a bug?
Last edited on May 27, 2020, 4:08 pm by atselitan · #1
atselitan
21 Posts
May 29, 2020, 5:21 amQuote from atselitan on May 29, 2020, 5:21 amGuys, don't ignore me please.
Guys, don't ignore me please.
admin
2,930 Posts
May 30, 2020, 2:37 pmQuote from admin on May 30, 2020, 2:37 pmCan you try to update to latest online (2.5.3)
Can you try to update to latest online (2.5.3)
Last edited on May 30, 2020, 2:38 pm by admin · #3
atselitan
21 Posts
May 31, 2020, 5:22 pmQuote from atselitan on May 31, 2020, 5:22 pmOk, I'll try. Thanks.
Ok, I'll try. Thanks.
atselitan
21 Posts
June 8, 2020, 2:16 pmQuote from atselitan on June 8, 2020, 2:16 pmHello!
Update to 2.5.3 was not solved my problem.
Additional screenshot from SSH console ("lsblk" command):
You can see what the problem disk looks like compared to "healthy"disks. Is that correct or not?
Hello!
Update to 2.5.3 was not solved my problem.
Additional screenshot from SSH console ("lsblk" command):
You can see what the problem disk looks like compared to "healthy"disks. Is that correct or not?
Last edited on June 10, 2020, 12:39 pm by atselitan · #5
atselitan
21 Posts
June 10, 2020, 10:06 amQuote from atselitan on June 10, 2020, 10:06 amHello!
Additional information about my issue:
After node reboot - osd.488 is down. And directory /var/lib/ceph/osd/ceph-488 is empty.
After i perform following command, directory /var/lib/ceph/osd/ceph-488 becomes contain files, and then osd.488 becomes UP.
ceph-volume simple scan /dev/sds1
Maybe i need to redeploy this OSD? How to perform it correctly?
Hello!
Additional information about my issue:
After node reboot - osd.488 is down. And directory /var/lib/ceph/osd/ceph-488 is empty.
After i perform following command, directory /var/lib/ceph/osd/ceph-488 becomes contain files, and then osd.488 becomes UP.
ceph-volume simple scan /dev/sds1
Maybe i need to redeploy this OSD? How to perform it correctly?
Last edited on June 10, 2020, 2:04 pm by atselitan · #6
atselitan
21 Posts
April 9, 2021, 5:12 amQuote from atselitan on April 9, 2021, 5:12 amHello!
The problem is still actual (see above, first post).
I have Petasan 2.7.2 and three OSDs with the same issue today.
The last of three disks was replaced one week ago.
Have any idea how to fix it?
Hello!
The problem is still actual (see above, first post).
I have Petasan 2.7.2 and three OSDs with the same issue today.
The last of three disks was replaced one week ago.
Have any idea how to fix it?
Last edited on April 9, 2021, 5:20 am by atselitan · #7
admin
2,930 Posts
April 9, 2021, 10:05 amQuote from admin on April 9, 2021, 10:05 amcan you do online update to 2.7.3 and see if it fixes it.
can you do online update to 2.7.3 and see if it fixes it.
atselitan
21 Posts
April 12, 2021, 6:13 amQuote from atselitan on April 12, 2021, 6:13 am
Quote from admin on April 9, 2021, 10:05 am
can you do online update to 2.7.3 and see if it fixes it.
Problem solved!
Thanks.
Quote from admin on April 9, 2021, 10:05 am
can you do online update to 2.7.3 and see if it fixes it.
Problem solved!
Thanks.
Missing journal information of new OSD after disk replacement
atselitan
21 Posts
Quote from atselitan on May 22, 2020, 12:20 pmHello
I have PetaSAN cluster upgraded to 2.5.1 version (cluster is more then two years old)
After broken disk replace and add new storage device, there is no information displayed about a journal of new storage device in WEB.
But using ssh console i can see information about existing journal (block.db) on nvme disk:
Is that alright or a bug?
Hello
I have PetaSAN cluster upgraded to 2.5.1 version (cluster is more then two years old)
After broken disk replace and add new storage device, there is no information displayed about a journal of new storage device in WEB.
But using ssh console i can see information about existing journal (block.db) on nvme disk:
Is that alright or a bug?
atselitan
21 Posts
Quote from atselitan on May 29, 2020, 5:21 amGuys, don't ignore me please.
Guys, don't ignore me please.
admin
2,930 Posts
Quote from admin on May 30, 2020, 2:37 pmCan you try to update to latest online (2.5.3)
Can you try to update to latest online (2.5.3)
atselitan
21 Posts
Quote from atselitan on May 31, 2020, 5:22 pmOk, I'll try. Thanks.
Ok, I'll try. Thanks.
atselitan
21 Posts
Quote from atselitan on June 8, 2020, 2:16 pmHello!
Update to 2.5.3 was not solved my problem.
Additional screenshot from SSH console ("lsblk" command):
You can see what the problem disk looks like compared to "healthy"disks. Is that correct or not?
Hello!
Update to 2.5.3 was not solved my problem.
Additional screenshot from SSH console ("lsblk" command):
You can see what the problem disk looks like compared to "healthy"disks. Is that correct or not?
atselitan
21 Posts
Quote from atselitan on June 10, 2020, 10:06 amHello!
Additional information about my issue:
After node reboot - osd.488 is down. And directory /var/lib/ceph/osd/ceph-488 is empty.After i perform following command, directory /var/lib/ceph/osd/ceph-488 becomes contain files, and then osd.488 becomes UP.
ceph-volume simple scan /dev/sds1Maybe i need to redeploy this OSD? How to perform it correctly?
Hello!
Additional information about my issue:
After node reboot - osd.488 is down. And directory /var/lib/ceph/osd/ceph-488 is empty.
After i perform following command, directory /var/lib/ceph/osd/ceph-488 becomes contain files, and then osd.488 becomes UP.
ceph-volume simple scan /dev/sds1
Maybe i need to redeploy this OSD? How to perform it correctly?
atselitan
21 Posts
Quote from atselitan on April 9, 2021, 5:12 amHello!
The problem is still actual (see above, first post).
I have Petasan 2.7.2 and three OSDs with the same issue today.
The last of three disks was replaced one week ago.
Have any idea how to fix it?
Hello!
The problem is still actual (see above, first post).
I have Petasan 2.7.2 and three OSDs with the same issue today.
The last of three disks was replaced one week ago.
Have any idea how to fix it?
admin
2,930 Posts
Quote from admin on April 9, 2021, 10:05 amcan you do online update to 2.7.3 and see if it fixes it.
can you do online update to 2.7.3 and see if it fixes it.
atselitan
21 Posts
Quote from atselitan on April 12, 2021, 6:13 amQuote from admin on April 9, 2021, 10:05 amcan you do online update to 2.7.3 and see if it fixes it.
Problem solved!
Thanks.
Quote from admin on April 9, 2021, 10:05 amcan you do online update to 2.7.3 and see if it fixes it.
Problem solved!
Thanks.