At some point, possibly due to a BIOS/firmware or kernel/OS update, the device naming on our SuperMicro Ceph servers has stopped being consistent after a reboot. e.g. the internal (OS) disks might be /dev/sda and sdb, or they might be /dev/sdbi and sdbj. This doesn't affect Ceph's day-to-day running, but it does break ceph-ansible because that tries to activate an OSD on the OS disk, which fails (safely). 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!) thanks, Dave -- ** Dave Holland ** Systems Support -- Informatics Systems Group ** ** dh3@xxxxxxxxxxxx ** Wellcome Sanger Institute, Hinxton, UK ** -- The Wellcome Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE. _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |