[Bug 254000] net/glusterfs: Directory entries corrupted

[bugzilla-noreply at freebsd.org]

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

            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 at FreeBSD.org
          Reporter: ltning-freebsd at anduin.net
                CC: daniel at morante.net
             Flags: maintainer-feedback?(daniel at morante.net)
                CC: daniel at morante.net

When using glusterfs - both old 3.x version and new 8.x - we observe that while
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 11.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 <filename>'
or 'ls -la <file>' or any other operation that directly accesses the file works
fine.

Again, we've seen this every time we've tested glusterfs, causing us to abort
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 elsewhere..

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