Bug 882769

Summary: Both NFS and CIFS are started automatically by default
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Jin Zhou <jzhou>
Component: sambaAssignee: Ira Cooper <ira>
Status: CLOSED WONTFIX QA Contact: storage-qa-internal <storage-qa-internal>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0CC: cmosher, ira, jarrpa, jcall, ndevos, nlevinki, poelstra, rhs-bugs, rjoseph, rwheeler, sgraf, vagarwal, vbellur
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: config
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-23 07:37:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 956495, 957769    

Description Jin Zhou 2012-12-03 04:53:04 UTC
Description of problem:

When a Gluster volume is started, by default both NFS and CIFS server processes are also started automatically. But since we do not support simultaneous CIFS and NFS access to the same volume, we should not autostart CIFS and NFS for the Gluster volume at the same time.

I suggest that we leave them both disabled by default. Or only make NFS server auto started.

Comment 2 Amar Tumballi 2012-12-03 06:51:34 UTC
> " But since we do not support simultaneous CIFS and NFS access to the same volume, we should not autostart CIFS and NFS for the Gluster volume at the same time."

Jin,

Where did you get the above confirmation? (any doc, someone stating it in email etc)

because, from storage philosophy, we think once a volume is started, it should be made available in all the access protocols as possible, and hence we start both CIFS and NFS when a volume starts.

Comment 3 Jin Zhou 2012-12-05 06:24:54 UTC
Hi Amar,

Certain protocols are not compatible to be enabled at the same time on the same volume.

While I'm still trying to get more complete picture, here are two email threads you can refer to

http://post-office.corp.redhat.com/archives/sme-storage/2012-August/msg00163.html

http://post-office.corp.redhat.com/archives/sme-storage/2012-November/msg00097.html

Thanks

Jin

Comment 4 Niels de Vos 2012-12-05 08:42:39 UTC
Note that the volume is only exported by samba when the samba service is enabled and running. If the samba service is disabled, the volume will only be exported over NFS.

I guess we could change the hook-scripts and have them check 'nfs.disable' before adding the volume to a smb.conf and restarting samba.

Comment 5 Amar Tumballi 2013-02-04 12:22:31 UTC
adding two more dev from Samba team to confirm the behavior on comment #3.

Comment 6 Scott Haines 2013-03-08 21:01:50 UTC
Per 03/05 email exchange w/ PM, targeting for Big Bend.

Comment 7 Christopher R. Hertel 2013-08-05 20:25:08 UTC
Re-confirming the behavior described in comment #3.
At this point in time, we do not consider NFS and SMB services to be compatible on top of GlusterFS.

Work is ongoing to make SMB compatible with other access methods.  Fixes to Gluster byte-range locking support, which were applied several months ago, are a major step toward protocol interoperability but new features (such as OpLock support) will be needed in order to fully synchronize behaviors.

Comment 11 Vivek Agarwal 2015-03-23 07:37:37 UTC
The product version of Red Hat Storage on which this issue was reported has reached End Of Life (EOL) [1], hence this bug report is being closed. If the issue is still observed on a current version of Red Hat Storage, please file a new bug report on the current version.







[1] https://rhn.redhat.com/errata/RHSA-2014-0821.html

Comment 12 Vivek Agarwal 2015-03-23 07:39:29 UTC
The product version of Red Hat Storage on which this issue was reported has reached End Of Life (EOL) [1], hence this bug report is being closed. If the issue is still observed on a current version of Red Hat Storage, please file a new bug report on the current version.







[1] https://rhn.redhat.com/errata/RHSA-2014-0821.html