On Tue, May 14, 2019 at 7:24 PM Bob R <bobr@xxxxxxxxxxxxxx> wrote: > > Does 'ceph-volume lvm list' show it? If so you can try to activate it with 'ceph-volume lvm activate 122 74b01ec2--124d--427d--9812--e437f90261d4' Good suggestion. If `ceph-volume lvm list` can see it, it can probably activate it again. You can activate it with the OSD ID + OSD FSID, or do: ceph-volume lvm activate --all You didn't say if the OSD wasn't coming up after trying to start it (the systemd unit should still be there for ID 122), or if you tried rebooting and that OSD didn't come up. The systemd unit is tied to both the ID and FSID of the OSD, so it shouldn't matter if the underlying device changed since ceph-volume ensures it is the right one every time it activates. > > Bob > > On Tue, May 14, 2019 at 7:35 AM Tarek Zegar <tzegar@xxxxxxxxxx> wrote: >> >> Someone nuked and OSD that had 1 replica PGs. They accidentally did echo 1 > /sys/block/nvme0n1/device/device/remove >> We got it back doing a echo 1 > /sys/bus/pci/rescan >> However, it reenumerated as a different drive number (guess we didn't have udev rules) >> They restored the LVM volume (vgcfgrestore ceph-8c81b2a3-6c8e-4cae-a3c0-e2d91f82d841 ; vgchange -ay ceph-8c81b2a3-6c8e-4cae-a3c0-e2d91f82d841) >> >> lsblk >> nvme0n2 259:9 0 1.8T 0 diskc >> ceph--8c81b2a3--6c8e--4cae--a3c0--e2d91f82d841-osd--data--74b01ec2--124d--427d--9812--e437f90261d4 253:1 0 1.8T 0 lvm >> >> We are stuck here. How do we attach an OSD daemon to the drive? It was OSD.122 previously >> >> Thanks >> >> _______________________________________________ >> ceph-users mailing list >> ceph-users@xxxxxxxxxxxxxx >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |