|
I have been plagued by errors of this kind
every so often, mainly because we are in a development phase and
we reboot our servers so frequently. If you start glusterd in
debug mode: sh$ glusterd --debug you can easily pinpoint exactly which volume/peer data is causing the initialization failure for mgmt/glusterd. In addition, from my own experiences, two of the leading reasons for failure include: a) Bad peer data if glusterd is somehow killed during an active peer probe operation, and b) I have noticed that if glusterd needs to update info for volume/brick (say "info" for volume testvol) in /var/lib/glusterd, it first renames /var/lib/glusterd/vols/testvol/info to info.tmp, and then creates a new file info, which is probably written into _freshly_. If glusterd were to crash at this point, it would cause failures in glusterd startup till this is manually resolved. Usually, moving info.tmp into info works for me. Thanks, Anirban On Saturday 12 April 2014 08:45 AM, 吴保川
wrote:
|
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
