Re: [ceph-users] Physical maintainance

Hi, Thanks guys, this worked like a charm. Activating the OSDs wasn't necessary: it seemed udev(7) helped me with that. Cheers, Kees On 13-07-16 14:47, Kees Meijs wrote: > So to sum up, I'd best: > > * set the noout flag > * stop the OSDs one by one > * shut down the physical node > *

Re: [ceph-users] Physical maintainance

Looks good. You can start several OSDs at a time as long as you have enough CPU and you're not saturating your drives or controllers. Jan > On 13 Jul 2016, at 15:09, Wido den Hollander wrote: > > >> Op 13 juli 2016 om 14:47 schreef Kees Meijs : >> >> >>

Re: [ceph-users] Physical maintainance

> Op 13 juli 2016 om 14:47 schreef Kees Meijs : > > > Thanks! > > So to sum up, I'd best: > > * set the noout flag > * stop the OSDs one by one > * shut down the physical node > * jank the OSD drives to prevent ceph-disk(8) from automaticly > activating at boot time

Re: [ceph-users] Physical maintainance

Thanks! So to sum up, I'd best: * set the noout flag * stop the OSDs one by one * shut down the physical node * jank the OSD drives to prevent ceph-disk(8) from automaticly activating at boot time * do my maintainance * start the physical node * reseat and activate the OSD

Re: [ceph-users] Physical maintainance

If you stop the OSDs cleanly then that should cause no disruption to clients. Starting the OSD back up is another story, expect slow request for a while there and unless you have lots of very fast CPUs on the OSD node, start them one-by-one and not all at once. Jan > On 13 Jul 2016, at

Re: [ceph-users] Physical maintainance

> Op 13 juli 2016 om 14:31 schreef Kees Meijs : > > > Hi Cephers, > > There's some physical maintainance I need to perform on an OSD node. > Very likely the maintainance is going to take a while since it involves > replacing components, so I would like to be well prepared. > >