Bug 1005786 - NFSv4 support
Summary: NFSv4 support
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: nfs
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Satish Mohan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-09 12:03 UTC by Marco Rodrigues
Modified: 2017-03-06 18:17 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-03-06 18:17:37 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Marco Rodrigues 2013-09-09 12:03:34 UTC
Description of problem:
To be able to connect directly from XenServer to GlusterFS using NFSv4 which have higher speeds.

Version-Release number of selected component (if applicable):
3.4.0

Additional info:
I did try using native NFSv4 from a CentOS 6.x machine and the speeds of version 4 of the protocol are great.

Comment 2 Federico Simoncelli 2014-07-28 09:59:26 UTC
I suggest to split out in a new BZ the implementation for:

- server-side file cloning
- server-side file pre-allocation

so that they can be implemented separately from nfs v4 support.

Comment 3 Niels de Vos 2014-08-28 17:30:59 UTC
NFSv4 will be provided through the integration with nfs-ganesha. There is some documentation available on the project space:
- https://forge.gluster.org/nfs-ganesha-and-glusterfs-integration/pages/Home

nfs-ganesha-2.1.0-5.el6 is available from EPEL-6 already:
- https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2025

There are some blog posts on the gluster.org website that talk about it too:
- http://blog.gluster.org/tag/ganesha/

Comment 5 Jiffin 2017-03-06 18:17:37 UTC
NFS-Ganesha provides support nfsv4 hence closing this bug


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