Bug 1471793 - USS + CIFS : ls on .snaps directory gives Input/Output error on CIFS mount
Summary: USS + CIFS : ls on .snaps directory gives Input/Output error on CIFS mount
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: snapshot
Version: rhgs-3.2
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: RHGS 3.2.0 Async
Assignee: Anoop C S
QA Contact: Anil Shah
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-17 12:53 UTC by Anil Shah
Modified: 2017-08-01 07:46 UTC (History)
6 users (show)

Fixed In Version: glusterfs-3.8.4-18.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 07:46:44 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2339 0 normal SHIPPED_LIVE glusterfs bug fix update 2017-08-01 11:45:56 UTC

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
Note You need to log in before you can comment on or make changes to this bug.