Re: Urgent :) Procedure for replacing Gluster Node on 3.8.12

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 9 June 2017 at 17:12, <lemonnierk@xxxxxxxxx> wrote:
Heh, on that, did you think to take a look at the Media_Wearout indicator ?
I recently learned that existed, and it explained A LOT.

Yah, that has been useful in the past for journal/cache ssd's that get a lot of writes. However all the stats on this boot SSD were ok, it just gave up the ghost. Internal controller failure maybe.

I've started the process as above, seems to be going ok - cluster is going to be unusable for the next couple of days.

Must admit this sort of process - replacing bricks and/or node is *very* stressful with gluster. That sick feeling in the stomach - will I have to restore everything from backups?

Shouldn't be this way.


--
Lindsay
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux