We recently encountered a problem with GlusterFS (7.x) when an application used the flock syscall on a GlusterFS path. If somehow two flock syscalls are made at the same time, the lock will never be released. And all future flock syscalls will wait forever.
This problem doesn't happen only on our infrastructure. There are a lot of bugreports, e.g.:
- https://docs.gluster.org/en/latest/release-notes/8.0/#bugs-addressed Show archive.org snapshot
- https://github.com/gluster/glusterfs/issues/1046 Show archive.org snapshot
- https://review.gluster.org/#/c/glusterfs/+/23794/ Show archive.org snapshot
- https://github.com/gluster/glusterfs/issues/982 Show archive.org snapshot
- https://github.com/gluster/glusterfs/issues/613 Show archive.org snapshot
- und viele mehr https://github.com/gluster/glusterfs/issues?q=is%3Aissue+flock+is%3Aclosed Show archive.org snapshot
There are also entries regarding flock or locking in general in each major release notes:
- https://docs.gluster.org/en/latest/release-notes/8.0/#bugs-addressed Show archive.org snapshot
- https://docs.gluster.org/en/latest/release-notes/8.0/#bugs-addressed Show archive.org snapshot
- https://docs.gluster.org/en/latest/release-notes/8.0/#bugs-addressed Show archive.org snapshot
- https://docs.gluster.org/en/latest/release-notes/8.0/#bugs-addressed Show archive.org snapshot
