Backport #21504
Updated by Nathan Cutler over 6 years ago
https://github.com/ceph/ceph/pull/17914 Ceph version 10.2.9 In a new deployment, after rebooting the nodes following error can be found in ceph-osd log files <pre> /var/log/ceph/ceph-osd.17.log:2017-08-01 08:52:05.824620 7f77c42b8b80 -1 ** ERROR: unable to open OSD superblock on /var/lib/ceph/osd/ceph-17: (2) No such file or directory /var/log/ceph/ceph-osd.3.log:2017-08-01 08:52:05.824323 7f46e90efb80 -1 ** ERROR: unable to open OSD superblock on /var/lib/ceph/osd/ceph-3: (2) No such file or directory /var/log/ceph/ceph-osd.5.log:2017-08-01 08:52:05.823254 7fcb53149b80 -1 ** ERROR: unable to open OSD superblock on /var/lib/ceph/osd/ceph-5: (2) No such file or directory /var/log/ceph/ceph-osd.9.log:2017-08-01 08:52:05.820776 7f86322bab80 -1 ** ERROR: unable to open OSD superblock on /var/lib/ceph/osd/ceph-9: (2) No such file or directory </pre> It turns out that ceph-disk is creating ceph-osd.target "wants" symlinks under /etc/systemd instead of /run/systemd: <pre> # ls -l /etc/systemd/system/ceph-osd.target.wants total 0 lrwxrwxrwx 1 root root 41 Sep 18 14:26 ceph-osd@0.service -> /usr/lib/systemd/system/ceph-osd@.service lrwxrwxrwx 1 root root 41 Sep 18 14:26 ceph-osd@1.service -> /usr/lib/systemd/system/ceph-osd@.service lrwxrwxrwx 1 root root 41 Sep 18 14:27 ceph-osd@2.service -> /usr/lib/systemd/system/ceph-osd@.service # ls -l /run/systemd/system/ceph-osd.target.wants ls: cannot access '/run/systemd/system/ceph-osd.target.wants': No such file or directory. </pre> After some debugging, I believe the commit https://github.com/ceph/ceph/commit/9b77b16b888b8efbf7d50d333e1880a6ec70d87a, has introduced a regression by using 'is_mounted' to check whether a path is mounted in 'systemd_start', while 'is_mounted' is supposedly used to check a device. A potential fix might be https://github.com/SUSE/ceph/pull/151