glusterfs.git/xlators/features/snapview-server, branch bug-deprecated

avoid memory leaks in snapview-server

2015-01-08T10:05:14+00:00

* snapview-server in readdirp, creates the inode for entries with names "." and
  ".." for each readdirp operation without creating dentries leading to memleak.
  It should have avoided creation of inodes for those entries

Change-Id: I3b2025fd10872fcc3303d0becec764ffd4e37601
BUG: 1179663
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.org/9404
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

uss/gluster: In SVS, check for entry-point in dict only if inode_ctx is

2014-12-16T13:33:44+00:00

not available

Change-Id: I990487003b712bf4aed8f54291417965f301655e
BUG: 1172430
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/9265
Tested-by: Gluster Build System 
Reviewed-by: Sachin Pandit 
Reviewed-by: Rajesh Joseph 
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Krishnan Parthasarathi

features/snapview-client: handle readdir requests differently for samba

2014-12-10T04:27:33+00:00

* For samba export, the entry point is also added to the readdir response.

Change-Id: I825c017e0f16db1f1890bb56e086f36e6558a1c2
BUG: 1168875
Signed-off-by: Raghavendra Bhat 
Reviewed-on: http://review.gluster.org/9218
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

uss/gluster: Send success on parent lookup of entry-point

2014-12-05T11:22:20+00:00

When a lookup sent to snapview-server for entry-point directory
protocol server first tries to resolve gfid of a parent directory.

looking up the parent gfid from a latest snapshot can fail if the
volume is a restored volume. As this gfid is already looked-up by
snapview-client, we can return success for the parent gfid.

Change-Id: Ic9b20561ef79b93032f07c3a81eae54a94e1747b
BUG: 1162498
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/9229
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra Bhat 
Reviewed-by: Rajesh Joseph 
Reviewed-by: Vijay Bellur

uss: CIFS gives error while accessing .snaps directory

2014-12-03T14:47:24+00:00

CIFS sends getxattr call while accessing .snaps directory.
snapview server should return ENODATA if getxattr is called
on .snaps folder. Also flush on .snaps folder should be handled.

Windows client sends and getxattr call on the parent folder
of .snaps with a special key to get the real filename of a file.
This is used by samba to do case insensitive check of files.

Fixed few FreeBSD compilation error.

bug: 1168875

Change-Id: I74d5cb4419568c8ed8709ba6d1ddff0e41392204
Signed-off-by: Rajesh Joseph 
Reviewed-on: http://review.gluster.org/9211
Reviewed-by: Raghavendra Bhat 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

USS : fill proper uid and gid during a access call from nfs

2014-12-01T16:04:06+00:00

Problem : when an user tries to access a file/folder for which
he does not have a proper permission required then fuse gives out
a proper error "Permission denied", but nfs does not give out that
error, rather he can access the file/folder. The reason being uid and
gid of call frame stack takes a default value of uid and gid which
point to root permission.

Solution : Set a proper uid and gid during a access call from nfs

Change-Id: Ib060706fde66ec7e60f242fab1f3e59122ed2245
BUG: 1167580
Signed-off-by: Sachin Pandit 
Reviewed-on: http://review.gluster.org/9194
Reviewed-by: Vijaikumar Mallikarjuna 
Reviewed-by: Rajesh Joseph 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

gluster/uss: Handle ESTALE in snapview client when NFS server restarted

2014-11-26T06:26:04+00:00

When NFS server is restarted inode-context is lost.
Nameless lookup will be sent to regular volume.
If the gfid is from virtual graph, lookup will fail
with ESTALE. We need to send a lookup to snapview server

Change-Id: I22920614f0d14cb90b53653fce95b6b70023eba6
BUG: 1166197
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/9153
Tested-by: Gluster Build System 
Reviewed-by: Sachin Pandit 
Reviewed-by: Vijay Bellur

uss/snapd: Handle readlink fops on snap view server

2014-11-14T14:27:36+00:00

Handle readlink fops in case of symlinks on
snap view server

BUG: 1162462
Change-Id: Ia08e9e9c1c61e06132732aa580c5a9fd5e7c449b
Signed-off-by: Avra Sengupta 
Reviewed-on: http://review.gluster.org/9102
Reviewed-by: Vijaikumar Mallikarjuna 
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

uss/gluster: creating file/directories inside .snaps should fail with

2014-11-13T14:55:11+00:00

EROFS

When an attempt is made to create file/directories inside .snaps, it
fails with wrong error message as "Stale file handle". It should fail
with "Read-only file system"

Change-Id: I3a812a0afc4762cbb71ab180b9394c866e576a66
BUG: 1159840
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/9039
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

uss/gluster: Move all uss related logs into subfolder

2014-11-12T11:23:59+00:00

For USS we have 1 snapd log per volume and as many snap logs for volume.
For example if there are 4 volumes having 256 snaps each and USS is
enabled than total number of logs under /var/log/glusterfs for USS would
be 1028 logs.

Total logs = (4(snapd per volume) + 4(volumes)*256(snaps)) = 1028

Hence, it makes sense to move into into sub-folder structure like

/var/log/glusterfs/snaps//

Change-Id: I29262e6458c3906916923cd67d1145d6ae10bec3
BUG: 1160534
Signed-off-by: vmallika 
Reviewed-on: http://review.gluster.org/9050
Tested-by: Gluster Build System 
Reviewed-by: Rajesh Joseph 
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Krishnan Parthasarathi