Yes the rbd's are not remapped at system boot time. I haven't run into a VM or system hang because this since I ran into it as part of investigating using RHEL 7.1 as a client distro. Yes remapping the rbd's in a startup script worked around the issue. > -----Original Message----- > From: Steve Dainard [mailto:sdainard@xxxxxxxx] > Sent: Friday, July 17, 2015 1:59 PM > To: Bruce McFarland > Cc: ceph-users@xxxxxxxxxxxxxx > Subject: Re: Workaround for RHEL/CentOS 7.1 rbdmap service > start warnings? > > Other than those errors, do you find RBD's will not be unmapped on system > restart/shutdown on a machine using systemd? Leaving the system hanging > without network connections trying to unmap RBD's? > > That's been my experience thus far, so I wrote an (overly simple) systemd > file to handle this on a per RBD basis. > > On Tue, Jul 14, 2015 at 1:15 PM, Bruce McFarland > <Bruce.McFarland@xxxxxxxxxxxxxxxx> wrote: > > When starting the rbdmap.service to provide map/unmap of rbd devices > > across boot/shutdown cycles the /etc/init.d/rbdmap includes > > /lib/lsb/init-functions. This is not a problem except that the rbdmap > > script is making calls to the log_daemon_* log_progress_* > > log_actiion_* functions that are included in Ubuntu 14.04 distro's, > > but are not in the RHEL 7.1/RHCS > > 1.3 distro. Are there any recommended workaround for boot time startup > > in RHEL/Centos 7.1 clients? > > > > > > _______________________________________________ > > 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