Hi Dave, On Thu, Jan 06, 2022 at 05:42:56PM +0000, Dave Holland wrote: > The right solution appears to be to configure ceph-ansible to use > /dev/disk/by-path device names, allowing for the expander IDs being > embedded in the device name -- so those would have to be set per-host > with host vars. Has anyone done that change from /dev/sd and > /dev/disk/by-path and have any advice, please? Is it a safe change, or > do I have to stick with /dev/sd names and modify the device list as a > host var, if/when the naming changes after a reboot? (Which would be > grotty!) We're using the /dev/disk/by-path device names in Ceph Ansible for the exact same reason, and while it's a bit annoying to setup initially due to the unique IDs in that path, it's much more robust indeed. We never had an issue when replacing a disk, they always get the same path as the disk being replaced. The only surprise we had was after upgrading from CentOS 7 to CentOS 8; the paths went from e.g. /dev/disk/by-path/pci-0000:00:10.2-ata-3.0 to /dev/disk/by-path/pci-0000:00:10.2-ata-3, presumably because of a newer driver in the new kernel, but that was an easy fix. We didn't convert from a /dev/sd* setup to using /dev/disk/by-path, but I don't think there's any gotcha; ceph-volume will simply follow the symlink and find the same block devices as before. Cheers, -- Ben _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |