Bug 1471793

Summary:	USS + CIFS : ls on .snaps directory gives Input/Output error on CIFS mount
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Anil Shah <ashah>
Component:	snapshot	Assignee:	Anoop C S <anoopcs>
Status:	CLOSED ERRATA	QA Contact:	Anil Shah <ashah>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.2	CC:	amukherj, asrivast, rcyriac, rhinduja, rhs-bugs, storage-qa-internal
Target Milestone:	---	Keywords:	Regression, ZStream
Target Release:	RHGS 3.2.0 Async
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.8.4-18.6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 07:46:44 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 Anil Shah 2017-07-17 12:53:54 UTC

Description of problem:

ls on .snaps directory gives Input/output error on cifs mount.
However .snaps is visible on windows client.

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

glusterfs-3.8.4-18.5.el7rhgs.x86_64

How reproducible:
100%


Steps to Reproduce:
1. Create dist-rep volume
2. Enable uss 
3. Create snapshot and activate it

Actual results:

ls on .snaps fails with input/output error

Expected results:

ls on .snaps directory should be successful.

Additional info:

Comment 6 Atin Mukherjee 2017-07-19 09:48:29 UTC

downstream patches:

https://code.engineering.redhat.com/gerrit/#/c/112756/
https://code.engineering.redhat.com/gerrit/#/c/112757/
https://code.engineering.redhat.com/gerrit/#/c/112759/

Comment 8 Anil Shah 2017-07-25 12:28:01 UTC

cd .snaps is accessible .
Bug verified on build 3.8.4-18.6

Comment 10 errata-xmlrpc 2017-08-01 07:46:44 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2339