Date: Mon, 25 Jan 2021 10:17:27 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 252989] net/glusterfs glusterfs mount not accessible if second node is down Message-ID: <bug-252989-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252989 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@FreeBSD.org Reporter: eimar.koort@tutamail.com CC: daniel@morante.net Flags: maintainer-feedback?(daniel@morante.net) CC: daniel@morante.net Created simple gluster volume.=20 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=3Dfbsd:/gluvol,mountprog=3D/usr/local/sbin/mou= nt_glusterfs 0 0 fbsd:/gluvol /mnt fusefs rw,late,backupvolfile-server=3Dfpi4:/gluvol,mountprog=3D/usr/local/sbin/mou= nt_glusterfs 0 0 Now. If one of them goes like "poweroff", then glusterfs mount becomes unaccessible. root@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@fbsd:~ # halt -p root@fpi4:~ # gluster peer status Number of Peers: 1 Hostname: fbsd Uuid: 8b93554c-7389-40fd-9447-b622b5c9a444 State: Peer in Cluster (Disconnected) root@fpi4:~ # ls -la /mnt total 0 ls: /mnt: Socket is not connected I would expect /mnt still to be accessible despite second node availabilty. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-252989-7788>