<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<font size="-1"><font face="Courier 10 Pitch">Hi everybody.<br>
<br>
I have two peers in the cluster and a 2-replica volume which
seems okey if it was not for one weird bit - when a peer reboots
then on that peer after a reboot I see:<br>
<br>
$ gluster volume status USERs <br>
Status of volume: USERs<br>
Gluster process TCP Port RDMA Port
Online Pid<br>
------------------------------------------------------------------------------<br>
Brick swir.direct:/00.STORAGE/2/0-GLUSTER-U<br>
SERs N/A N/A
N N/A <br>
Brick dzien.direct:/00.STORAGE/2/0-GLUSTER-<br>
USERs 49152 0
Y 57338<br>
Self-heal Daemon on localhost N/A N/A
Y 4302 <br>
Self-heal Daemon on dzien.direct N/A N/A
Y 57359<br>
<br>
Task Status of Volume USERs<br>
------------------------------------------------------------------------------<br>
There are no active volume tasks<br>
<br>
I do not suppose it's expected.<br>
On such rebooted node I see:<br>
$ systemctl status -l glusterd<br>
● glusterd.service - GlusterFS, a clustered file-system server<br>
Loaded: loaded (/usr/lib/systemd/system/glusterd.service;
enabled; vendor preset: enabled)<br>
Drop-In: /etc/systemd/system/glusterd.service.d<br>
└─override.conf<br>
Active: active (running) since Mon 2020-06-29 21:37:36 BST;
13h ago<br>
Docs: <a class="moz-txt-link-freetext" href="man:glusterd(8)">man:glusterd(8)</a><br>
Process: 4071 ExecStart=/usr/sbin/glusterd -p
/var/run/glusterd.pid --log-level $LOG_LEVEL $GLUSTERD_OPTIONS
(code=exited, status><br>
Main PID: 4086 (glusterd)<br>
Tasks: 20 (limit: 101792)<br>
Memory: 28.9M<br>
CGroup: /system.slice/glusterd.service<br>
├─4086 /usr/sbin/glusterd -p /var/run/glusterd.pid
--log-level INFO<br>
└─4302 /usr/sbin/glusterfs -s localhost --volfile-id
shd/USERs -p /var/run/gluster/shd/USERs/USERs-shd.pid -l
/var/log/g><br>
<br>
Jun 29 21:37:36 swir.private.pawel systemd[1]: Starting
GlusterFS, a clustered file-system server...<br>
Jun 29 21:37:36 swir.private.pawel systemd[1]: Started
GlusterFS, a clustered file-system server.<br>
<br>
And I do not see any other apparent problems nor errors.<br>
On that node I manually:<br>
$ systemctl restart glusterd.service<br>
and...<br>
<br>
$ gluster volume status USERs <br>
Status of volume: USERs<br>
Gluster process TCP Port RDMA Port
Online Pid<br>
------------------------------------------------------------------------------<br>
Brick swir.direct:/00.STORAGE/2/0-GLUSTER-U<br>
SERs 49152 0
Y 103225<br>
Brick dzien.direct:/00.STORAGE/2/0-GLUSTER-<br>
USERs 49152 0
Y 57338<br>
Self-heal Daemon on localhost N/A N/A
Y 103270<br>
Self-heal Daemon on dzien.direct N/A N/A
Y 57359<br>
<br>
Is not a puzzle??? I'm on glusterfs-7.6-1.el8.x86_64<br>
I hope somebody can share some thoughts.<br>
many thanks, L.<br>
<br>
</font></font>
</body>
</html>