Device is not available after zap
Hi, With v15.2.8, after zap a device on OSD node, it's still not available. The reason is "locked, LVM detected". If I reboot the whole OSD node, then the device will be available. There must be something no being cleaned up. Any clues? Thanks! Tony
I checked pvscan, vgscan, lvscan and "ceph-volume lvm list" on the OSD node, that zapped device doesn't show anywhere. Anything missing? Thanks! Tony ________________________________________ From: Tony Liu <tonyliu0592@hotmail.com> Sent: February 7, 2021 05:27 PM To: ceph-users Subject: [ceph-users] Device is not available after zap Hi, With v15.2.8, after zap a device on OSD node, it's still not available. The reason is "locked, LVM detected". If I reboot the whole OSD node, then the device will be available. There must be something no being cleaned up. Any clues? Thanks! Tony _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
I built a new cluster from scratch, everything works fine. Could anyone help to find out what is stuck here? Another issue, devices don't show up after adding a host, could be the same cause. Any details about the workflow would be helpful too, like how mon gets devices when a host is added, is it pushed by something (mgr?) or pulled by mon? Thanks! Tony
-----Original Message----- From: Tony Liu <tonyliu0592@hotmail.com> Sent: Sunday, February 7, 2021 5:32 PM To: ceph-users <ceph-users@ceph.io> Subject: [ceph-users] Re: Device is not available after zap
I checked pvscan, vgscan, lvscan and "ceph-volume lvm list" on the OSD node, that zapped device doesn't show anywhere. Anything missing?
Thanks! Tony ________________________________________ From: Tony Liu <tonyliu0592@hotmail.com> Sent: February 7, 2021 05:27 PM To: ceph-users Subject: [ceph-users] Device is not available after zap
Hi,
With v15.2.8, after zap a device on OSD node, it's still not available. The reason is "locked, LVM detected". If I reboot the whole OSD node, then the device will be available. There must be something no being cleaned up. Any clues?
Thanks! Tony _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
Sorry, not much to say other than a "me too". i spent a week testing ceph configurations.. it should have only been 2 days. but a huge amount of my time was wasted because I needed to do a full reboot on the hardware. on a related note: sometimes "zap" didnt fully clean things up. I had to manually go in and clean up vgs. or pvs. or sometimes wipefs -a so, in theory, this could be a linux LVM bug. but if I recall, i was doing this with ceph octopus, and centos 7.9 ----- Original Message ----- From: "Tony Liu" <tonyliu0592@hotmail.com> To: "ceph-users" <ceph-users@ceph.io> Sent: Sunday, February 7, 2021 5:31:53 PM Subject: [ceph-users] Re: Device is not available after zap I checked pvscan, vgscan, lvscan and "ceph-volume lvm list" on the OSD node, that zapped device doesn't show anywhere. Anything missing? Thanks! Tony ________________________________________ From: Tony Liu <tonyliu0592@hotmail.com> Sent: February 7, 2021 05:27 PM To: ceph-users Subject: [ceph-users] Device is not available after zap Hi, With v15.2.8, after zap a device on OSD node, it's still not available. The reason is "locked, LVM detected". If I reboot the whole OSD node, then the device will be available. There must be something no being cleaned up. Any clues? Thanks! Tony
Are you running zap on the lvm volume, or the underlying block device? If you are running it against the lvm volume, it sounds like you need to run it against the block device so it wipes the lvm volumes as well. (Disclaimer: I don't run Ceph in this configuration) On Wed, Feb 10, 2021 at 10:24 AM Philip Brown <pbrown@medata.com> wrote:
Sorry, not much to say other than a "me too". i spent a week testing ceph configurations.. it should have only been 2 days. but a huge amount of my time was wasted because I needed to do a full reboot on the hardware.
on a related note: sometimes "zap" didnt fully clean things up. I had to manually go in and clean up vgs. or pvs. or sometimes wipefs -a
so, in theory, this could be a linux LVM bug. but if I recall, i was doing this with ceph octopus, and centos 7.9
----- Original Message ----- From: "Tony Liu" <tonyliu0592@hotmail.com> To: "ceph-users" <ceph-users@ceph.io> Sent: Sunday, February 7, 2021 5:31:53 PM Subject: [ceph-users] Re: Device is not available after zap
I checked pvscan, vgscan, lvscan and "ceph-volume lvm list" on the OSD node, that zapped device doesn't show anywhere. Anything missing?
Thanks! Tony ________________________________________ From: Tony Liu <tonyliu0592@hotmail.com> Sent: February 7, 2021 05:27 PM To: ceph-users Subject: [ceph-users] Device is not available after zap
Hi,
With v15.2.8, after zap a device on OSD node, it's still not available. The reason is "locked, LVM detected". If I reboot the whole OSD node, then the device will be available. There must be something no being cleaned up. Any clues?
Thanks! Tony _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
-- This e-mail and all information in, attached to, or linked via this e-mail (together the ‘e-mail’) is confidential and may be legally privileged. It is intended solely for the intended addressee(s). Access to, or any onward transmission, of this e-mail by any other person is not authorised. If you are not the intended recipient, you are requested to immediately alert the sender of this e-mail and to immediately delete this e-mail. Any disclosure in any form of all or part of this e-mail, or of any the parties to it, including any copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. This e-mail is not, and is not intended to be, and should not be construed as being, (a) any offer, solicitation, or promotion of any kind; (b) the basis of any investment or other decision(s); (c) any recommendation to buy, sell or transact in any manner any good(s), product(s) or service(s), nor engage in any investment(s) or other transaction(s) or activities; or (d) the provision of, or related to, any advisory service(s) or activities, including regarding any investment, tax, legal, financial, accounting, consulting or any other related service(s).
ive always run it against the block dev ----- Original Message ----- From: "Matt Wilder" <matt.wilder@bitmex.com> To: "Philip Brown" <pbrown@medata.com> Cc: "ceph-users" <ceph-users@ceph.io> Sent: Wednesday, February 10, 2021 12:06:55 PM Subject: Re: [ceph-users] Re: Device is not available after zap Are you running zap on the lvm volume, or the underlying block device? If you are running it against the lvm volume, it sounds like you need to run it against the block device so it wipes the lvm volumes as well. (Disclaimer: I don't run Ceph in this configuration) On Wed, Feb 10, 2021 at 10:24 AM Philip Brown <pbrown@medata.com> wrote:
Sorry, not much to say other than a "me too". i spent a week testing ceph configurations.. it should have only been 2 days. but a huge amount of my time was wasted because I needed to do a full reboot on the hardware.
on a related note: sometimes "zap" didnt fully clean things up. I had to manually go in and clean up vgs. or pvs. or sometimes wipefs -a
so, in theory, this could be a linux LVM bug. but if I recall, i was doing this with ceph octopus, and centos 7.9
I had something similar a while ago, can't remember how I solved it sorry, but it is not a lvm bug. Also posted it here. To bad this is still not fixed.
-----Original Message----- Cc: ceph-users <ceph-users@ceph.io> Subject: [ceph-users] Re: Device is not available after zap
ive always run it against the block dev
----- Original Message ----- From: "Matt Wilder" <matt.wilder@bitmex.com> To: "Philip Brown" <pbrown@medata.com> Cc: "ceph-users" <ceph-users@ceph.io> Sent: Wednesday, February 10, 2021 12:06:55 PM Subject: Re: [ceph-users] Re: Device is not available after zap
Are you running zap on the lvm volume, or the underlying block device?
If you are running it against the lvm volume, it sounds like you need to run it against the block device so it wipes the lvm volumes as well. (Disclaimer: I don't run Ceph in this configuration)
On Wed, Feb 10, 2021 at 10:24 AM Philip Brown <pbrown@medata.com> wrote:
Sorry, not much to say other than a "me too". i spent a week testing ceph configurations.. it should have only been 2 days. but a huge amount of my time was wasted because I needed to do a full reboot on the hardware.
on a related note: sometimes "zap" didnt fully clean things up. I had to manually go in and clean up vgs. or pvs. or sometimes wipefs -a
so, in theory, this could be a linux LVM bug. but if I recall, i was doing this with ceph octopus, and centos 7.9
ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
To update, the OSD had data on HDD and DB on SSD. After "ceph orch osd rm 12 --replace --force" and wait till rebalancing is done and daemon is stopped, I ran "ceph orch device zap ceph-osd-2 /dev/sdd" to zap the device. It cleared PV, VG and LV for data device, but not DB device. DB device issue is being discussed in another thread. Eventually, I restart the active mgr, then the device shows up available. Not sure what was stuck in mgr. Thanks! Tony ________________________________________ From: Marc <Marc@f1-outsourcing.eu> Sent: February 10, 2021 12:21 PM To: Philip Brown; Matt Wilder Cc: ceph-users Subject: [ceph-users] Re: Device is not available after zap I had something similar a while ago, can't remember how I solved it sorry, but it is not a lvm bug. Also posted it here. To bad this is still not fixed.
-----Original Message----- Cc: ceph-users <ceph-users@ceph.io> Subject: [ceph-users] Re: Device is not available after zap
ive always run it against the block dev
----- Original Message ----- From: "Matt Wilder" <matt.wilder@bitmex.com> To: "Philip Brown" <pbrown@medata.com> Cc: "ceph-users" <ceph-users@ceph.io> Sent: Wednesday, February 10, 2021 12:06:55 PM Subject: Re: [ceph-users] Re: Device is not available after zap
Are you running zap on the lvm volume, or the underlying block device?
If you are running it against the lvm volume, it sounds like you need to run it against the block device so it wipes the lvm volumes as well. (Disclaimer: I don't run Ceph in this configuration)
On Wed, Feb 10, 2021 at 10:24 AM Philip Brown <pbrown@medata.com> wrote:
Sorry, not much to say other than a "me too". i spent a week testing ceph configurations.. it should have only been 2 days. but a huge amount of my time was wasted because I needed to do a full reboot on the hardware.
on a related note: sometimes "zap" didnt fully clean things up. I had to manually go in and clean up vgs. or pvs. or sometimes wipefs -a
so, in theory, this could be a linux LVM bug. but if I recall, i was doing this with ceph octopus, and centos 7.9
ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
participants (4)
-
Marc
-
Matt Wilder
-
Philip Brown
-
Tony Liu