Bug 1374462 - Ganesha needs asynchronous blocking byte range locks that can be cancelled
Summary: Ganesha needs asynchronous blocking byte range locks that can be cancelled
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: libgfapi
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact: Sudhir D
URL: https://sourceforge.net/p/nfs-ganesha...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-08 17:44 UTC by Frank Filz
Modified: 2018-11-20 09:42 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-20 09:10:23 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Frank Filz 2016-09-08 17:44:15 UTC
Description of problem:

As a multi-threaded NFS server, Ganesha ideally needs to be able to have blocking byte range locks without occupying a thread for each, or polling. They also need to be cancelable.

Comment 1 Vijay Bellur 2018-11-20 09:42:52 UTC
Migrated to github:

https://github.com/gluster/glusterfs/issues/602

Please follow the github issue for further updates on this bug.


Note You need to log in before you can comment on or make changes to this bug.