Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1194380

Summary:	"mount error(6): No such device or address " when mounting gluster volume as samba-share
Product:	[Community] GlusterFS	Reporter:	mauro fattore <maurof>
Component:	gluster-smb	Assignee:	bugs <bugs>
Status:	CLOSED EOL	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	3.6.2	CC:	bugs, lmohanty, maurof, pgurusid, rjoseph, stefano.stagnaro
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-23 12:48:12 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:

Description mauro fattore 2015-02-19 17:02:25 UTC

Description of problem:
S20 S21  storage-gluster nodes with CTDB

volume named "SAMBA" active


Volume Name: SAMBA
Type: Distributed-Replicate
Volume ID: a1e83f05-b63c-4c28-af92-8c505b113233
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: s20gfs.ovirt.prisma:/gluster/VOL_SAMBA/b1
Brick2: s21gfs.ovirt.prisma:/gluster/VOL_SAMBA/b2
Brick3: s20gfs.ovirt.prisma:/gluster/VOL_SAMBA/b3
Brick4: s21gfs.ovirt.prisma:/gluster/VOL_SAMBA/b4
Options Reconfigured:
storage.batch-fsync-delay-usec: 0
performance.quick-read: off
performance.read-ahead: off
performance.io-cache: off
performance.stat-prefetch: off
cluster.eager-lock: enable
network.remote-dio: enable
cluster.quorum-type: auto
cluster.server-quorum-type: server
storage.owner-uid: 36
storage.owner-gid: 36
server.allow-insecure: on


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


How reproducible:


Steps to Reproduce:

1. configure Gluster volume "SAMBA"  as samba-share on Storage nodes S20 S21:

/etc/samba/smb.conf:

 [gluster-SAMBA]
comment = For samba share of volume SAMBA
vfs objects = glusterfs
glusterfs:volume = SAMBA
glusterfs:logfile = /var/log/samba/glusterfs-SAMBA.%M.log
glusterfs:loglevel = 7
path = /
read only = no
guest ok = yes
valid users = jon


2. gluster-SAMBA is correctly listed at client-side

sudo smbclient -L  nas.ovirt.prisma -U jon

Domain=[MYGROUP] OS=[Unix] Server=[Samba 3.6.23-12.el6]

	Sharename       Type      Comment
	---------       ----      -------
	share           Disk      Gluster and CTDB based share
	share2          Disk      Second Gluster and CTDB based share
	gluster-SAMBA   Disk      For samba share of volume SAMBA
	IPC$            IPC       IPC Service (Samba Server Version 3.6.23-12.el6)
	jon             Disk      Home Directories
Domain=[MYGROUP] OS=[Unix] Server=[Samba 3.6.23-12.el6]

	Server               Comment
	---------            -------

	Workgroup            Master
	---------            -------



3. try mounting from client :

   sudo mount -t cifs \\\\nas.ovirt.prisma\\gluster-SAMBA /mnt/prova -o username=jon
Password: 
Retrying with upper case share name
mount error(6): No such device or address
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)


Actual results:

failing with message: 
mount error(6): No such device or address

Expected results:

gluster-SAMBA correctly mounted

Additional info:

Comment 1 Lalatendu Mohanty 2015-02-24 12:42:46 UTC

Not sure if the mount command have some issue. I usually use below

mount -t cifs -o username=<username>,password=<smbpassword> //Server1_IP/testvol /mnt/cifs

Comment 2 Poornima G 2015-02-24 12:57:43 UTC

Could you provide the following information:

- Version of gluster, samba, ctdb
- output of smbstatus
- Samba logs, can be found in /var/log/samba/log.<client ip>

Also could you add the below option in your smb.conf, in the gluster share section:
kernel share modes = no

I also see valid users = jon, make sure the samba is able authenticate user 'jon'.

Comment 3 mauro fattore 2015-02-24 13:03:32 UTC

New deployment of OVirt3.5.1/GlusterFS is ongoing.
As soon as the environment is ready i 'll try to reproduce the test-case and give requested  details

Comment 4 rjoseph 2016-08-23 12:48:12 UTC

This bug is being closed as GlusterFS-3.6 is nearing its End-Of-Life and only important security bugs will be fixed. If you still face this bug with the newer GlusterFS versions, please open a new bug.