Date: Wed, 03 Mar 2021 22:44:02 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 254000] net/glusterfs: Directory entries corrupted Message-ID: <bug-254000-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254000 Bug ID: 254000 Summary: net/glusterfs: Directory entries corrupted Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: ltning-freebsd@anduin.net CC: daniel@morante.net Flags: maintainer-feedback?(daniel@morante.net) CC: daniel@morante.net When using glusterfs - both old 3.x version and new 8.x - we observe that w= hile most (all?) files are correctly replicated, listing directories do not show= all files. Tested with older and current glusterfs on FreeBSD versions from 10.x via 1= 1.x to (now) 12.2. Example: Source filesystem has ~12k files across ~100 directories. We rsync this to a gluster volume mounted on /mnt. Afterwards we run find /mnt -type f | wc -l on two different nodes in the cluster. The numbers are not the same. Then we do, on two nodes find /mnt -type f | sort > /mnt/$(hostname).lst When comparing the two, the sets of files on the two seem different. HOWEVER: When performing spot-checks, we DO find allegedly missing files in= the filesystem, but ONLY when referring to it directly. An 'ls' in the directory that contains a "missing" file will not show the file, but a 'file <filenam= e>' or 'ls -la <file>' or any other operation that directly accesses the file w= orks fine. Again, we've seen this every time we've tested glusterfs, causing us to abo= rt our attempts. Now that we have a "fresh" maintainer, I'm hoping perhaps this can be solved. I don't know if the problem is in gluster or fuse or elsewhe= re.. --=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-254000-7788>