Bug 1241142 - USS : Unable to access .snaps directory from CIFS mount
Summary: USS : Unable to access .snaps directory from CIFS mount
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: snapshot
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: ---
Assignee: rjoseph
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1223636
TreeView+ depends on / blocked
 
Reported: 2015-07-08 14:42 UTC by Anil Shah
Modified: 2017-02-21 06:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-21 06:52:31 UTC
Embargoed:


Attachments (Terms of Use)

Description Anil Shah 2015-07-08 14:42:34 UTC
Description of problem:

Ater enabling USS, unable to cd .snaps folder from CIFS mount. However was able to access .snaps from FUSE mount.

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

glusterfs-3.7.1-8.el6rhs.x86_64


How reproducible:

1/1

Steps to Reproduce:
1. Create 2*2 distribute-replicate volume
2. Mount volume as CIFS 
3. Create snapshot and activate it

Actual results:

Unable to access .snaps folder from CIFS mount

Expected results:

Should be able to access .snaps folder

Additional info:

[root@darkknightrises samba]# gluster v info vol0
 
Volume Name: vol0
Type: Distributed-Replicate
Volume ID: 80478eac-83b0-4a61-aed8-090be20bfb31
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: 10.70.33.214:/rhs/brick1/b001
Brick2: 10.70.33.219:/rhs/brick1/b002
Brick3: 10.70.33.225:/rhs/brick1/b003
Brick4: 10.70.44.13:/rhs/brick1/b004
Options Reconfigured:
performance.readdir-ahead: on
features.uss: enable
features.quota: on
features.inode-quota: on
features.quota-deem-statfs: on
features.barrier: disable
features.show-snapshot-directory: enable
server.allow-insecure: on
performance.stat-prefetch: off
storage.batch-fsync-delay-usec: 0
snap-activate-on-create: enable
[root@darkknightrises samba]#

Comment 3 Raghavendra Bhat 2015-07-09 07:19:59 UTC
While analysing the issue, I found that for some reason the protocol/client xlator sitting in the client graph (i.e. the graph present in the samba daemon), which talks to the snapd is not able to get the port number of the snapd from glusterd. 

There are no errors logged by glusterd regarding this failure of client to get the port number.

For more debugging the volume had to be restarted and it seems since then it has been working fine.

Still not sure why client xlator was not able to get the port number of the snapd from glusterd. Can be investigated further if the issue happens again.

Comment 5 Anil Shah 2015-07-11 11:37:35 UTC
Hit this issue again. Where i am unable to access .snaps.

I had cifs mount. Was doing file some files operation and creating snapshots.
Then then connected to samba share through GUI. Could not see .snaps folder.

Unmounted the cifs mount, mount it again. Could not see .snaps folder.
Restarted the glusterd, smb and volume. Still .snaps is not accessible.

Comment 6 rjoseph 2017-02-21 06:52:31 UTC
This issue seems to be fixed and is tested multiple times. Therefore I am closing this bug. Please feel free to reopen the issue if hit again.


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