Hi, Would I take this to understand that this may be a known issue with udev on RHEL then? We will for now add them to the fstab. Thanks, derek On 1/25/14, 9:23 PM, Michael J. Kidd wrote: > While clearly not optimal for long term flexibility, I've found that > adding my OSD's to fstab allows the OSDs to mount during boot, and they > start automatically when they're already mounted during boot. > > Hope this helps until a permanent fix is available. > > Michael J. Kidd > Sr. Storage Consultant > Inktank Professional Services > > > On Fri, Jan 24, 2014 at 9:08 PM, Derek Yarnell <derek@xxxxxxxxxxxxxx > <mailto:derek@xxxxxxxxxxxxxx>> wrote: > > So we have a test cluster, and two production clusters all running on > RHEL6.5. Two are running Emperor and one of them running Dumpling. On > all of them our OSDs do not start at boot it seems via the udev rules. > The OSDs were created with ceph-deploy and are all GPT. The OSDs are > visable with `ceph-disk list` and running `/usr/sbin/ceph-disk-activate > {device}` mounts and adds them. Running a `partprobe {device}` does not > seem to trigger the udev rule at all. > > I had found this issue[1] but we are definitely running code that was > released after this ticket was closed. Has there been anyone else that > has problems with udev on RHEL mounting their OSDs? > > [1] - http://tracker.ceph.com/issues/5194 > > Thanks, > derek > > -- > Derek T. Yarnell > University of Maryland > Institute for Advanced Computer Studies > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx <mailto:ceph-users@xxxxxxxxxxxxxx> > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > > -- Derek T. Yarnell University of Maryland Institute for Advanced Computer Studies _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |