[Bugs] [Bug 1168875] [USS]: browsing .snaps directory with CIFS fails with "Invalid argument"

bugzilla at redhat.com bugzilla at redhat.com
Tue Dec 16 06:16:40 UTC 2014


https://bugzilla.redhat.com/show_bug.cgi?id=1168875

Raghavendra Bhat <rabhat at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|POST                        |MODIFIED



--- Comment #26 from Raghavendra Bhat <rabhat at redhat.com> ---
As of now, the entry-point dentry (.snaps by default) is not sent as part of
readdir response (not even in ls -a it is visible.) Because, if one does cp -r
of a directory or entire glusterfs volume, then even the snapshot data will
also be copied. One has to explicitly give the .snaps name while accessing
snapshots (such as "ls .snaps" or "cd .snaps").

This causes problems in windows, as in windows explorer .snaps entry will not
be seen. If the path of .snaps is given in the address bar (like it is done for
fuse and nfs), then windows instead of sending a lookup on the entry-point,
will send readdir on its parent, and checks if the dentry for the entry-point
is present in readdir response or not. And since uss is not sending the
entry-point in readdir, the access to is denies by windows.

So to handle this the following method is used.

Samba while starting gfapi (via the glusterfs plugin for samba), should give a
xlator option that is recognized by snapview-client (the option is path in the
glusterfs volume that is exported via samba or used as the share for windows).
When the above option is set to a valid path, then snapview-client will add the
dentry of the entry-point in the readdir response coming on that path. It is
added only for the exported directory because, again in windows explorer if one
selects all the directories/folders and copies, there is a possibility of
snapshot data being copied from the subdirectories of the share.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list