...and here's the statedump of the client, snapd and brick snap
processes from the 4.1 test cluster.
(File names are as outputted from the GlusterD processes, so it looks
like the `snapd` daemon
has an off-by-one error in the statedump.)

Thanks,
Riccardo

Attachment: glusterdump.1726.dump.1532446976.gz
Description: application/gzip

Attachment: run-gluster-snaps-39f9f186c67f418a989f783c3289d166-brick3.5446.dump.1532446840.gz
Description: application/gzip

Attachment: napd-glusterfs.5482.dump.1532446843.gz
Description: application/gzip

_______________________________________________
Gluster-users mailing list
[email protected]
https://lists.gluster.org/mailman/listinfo/gluster-users

Reply via email to