[Bug 252989] net/glusterfs glusterfs mount not accessible if second node is down
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Jan 27 04:37:38 UTC 2021
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252989
--- Comment #3 from eimar.koort at tutamail.com ---
Hello,
Do You have gluster and client(s) on separate hosts?
In my setup i have only 2 hosts both acting as gluster server and clients.
fstab on one host:
fpi4:/gluvol /mnt fusefs
rw,late,backup-volfile-servers=fpi4:fbsd:/gluvol,mountprog=/usr/local/sbin/mount_glusterfs
0 0
And it still gives me "socket error". Note the "df" output.
root at fpi4:~ # mount |grep mnt
/dev/fuse on /mnt (fusefs)
root at fpi4:~ # df -h /mnt
Filesystem Size Used Avail Capacity Mounted on
/dev/fuse 0B 0B 0B 100% /mnt
root at fpi4:~ # ls -la /mnt
total 0
ls: /mnt: Socket is not connected
root at fpi4:~ # gluster peer status
Number of Peers: 1
Hostname: fbsd
Uuid: 8b93554c-7389-40fd-9447-b622b5c9a444
State: Peer in Cluster (Disconnected)
Second host is down. Not touching first node (fpi4) and powering on virtualbox.
oot at fpi4:~ # gluster peer status
Number of Peers: 1
Hostname: fbsd
Uuid: 8b93554c-7389-40fd-9447-b622b5c9a444
State: Peer in Cluster (Connected)
root at fpi4:~ # df -h /mnt
Filesystem Size Used Avail Capacity Mounted on
/dev/fuse 13G 2.5G 11G 19% /mnt
root at fpi4:~ # ls -la /mnt
total 5
drwxr-xr-x 3 root wheel 4 Jan 25 11:13 .
drwxr-xr-x 21 root wheel 512 Jan 27 04:27 ..
-rw-r--r-- 1 root wheel 34 Jan 25 11:14 test
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list