[Bug 252989] net/glusterfs glusterfs mount not accessible if second node is down

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252989

            Bug ID: 252989
           Summary: net/glusterfs glusterfs mount not accessible if second
                    node is down
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: eimar.koort at tutamail.com
                CC: daniel at morante.net
             Flags: maintainer-feedback?(daniel at morante.net)
                CC: daniel at morante.net

Created simple gluster volume. 
One "node" is rasbperry pi 4 13.0-ALPHA1  (fpi4)
Second "node is virtualbox FreeBSD 12.2-RELEASE-p1 (fbsd)
Both have latest Glusterfs 8.0_2

/etc/fstab contains line(s) accordingly:

fpi4:/gluvol /mnt fusefs
rw,late,backupvolfile-server=fbsd:/gluvol,mountprog=/usr/local/sbin/mount_glusterfs
0 0

fbsd:/gluvol /mnt fusefs
rw,late,backupvolfile-server=fpi4:/gluvol,mountprog=/usr/local/sbin/mount_glusterfs
0 0

Now. If one of them goes like "poweroff", then glusterfs mount becomes
unaccessible.

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 25 09:11 ..
-rw-r--r--   1 root  wheel   34 Jan 25 11:14 test.txt

root at fbsd:~ # halt -p

root at fpi4:~ # gluster peer status
Number of Peers: 1

Hostname: fbsd
Uuid: 8b93554c-7389-40fd-9447-b622b5c9a444
State: Peer in Cluster (Disconnected)

root at fpi4:~ # ls -la /mnt
total 0
ls: /mnt: Socket is not connected


I would expect /mnt still to be accessible despite second node availabilty.

-- 
You are receiving this mail because:
You are the assignee for the bug.