On 2018/02/27 4:23 pm, John Spray wrote:
On Tue, Feb 27, 2018 at 6:37 PM, Andre Goree <andre@xxxxxxxxxx> wrote:
Is it still considered best practice to set 'noout' for OSDs that will
be
going under maintenance, e.g., rebooting an OSD ndoe for a kernel
update?
I ask, because I've set this twice now during times which the OSDs
would
only momentarily be 'out', however each time I've done this, the OSDs
have
become unusable and I've had to rebuild them.
Can you be more specific about "unusable"? Marking an OSD noout is of
course not meant to harm it!
John
Sorry I should've been more specific. I believe I run into an issue
where the journal for a given OSD is corrupt and thus prevents the OSD
from booting.
I did just find a way to flush a journal from an OSD earlier today (I
hadn't actually troubleshot much and didn't look into getting the OSD
back, as I should've) which I probably should've done and wouldn't have
had to re-deploy anything, lol.
In any case, if I run into issues again if/when I need to try this, I'll
make my way back to this thread. For right now there is no issue and
surely my ignorance with Ceph is showing, haha.
Thanks for the replies.
--
Andre Goree
-=-=-=-=-=-
Email - andre at drenet.net
Website - http://blog.drenet.net
PGP key - http://www.drenet.net/pubkey.html
-=-=-=-=-=-
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
