<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-text-flowed" style="font-family: -moz-fixed;
font-size: 13px;" lang="x-unicode">Hi,
<br>
<br>
We couldn't delete any files and directories when connecting
glusterfs to windows via NFS.
<br>
We could make/change files and directories.
<br>
Although it has written that glusterfs can be connected with
windows NFS client in the page shown below.
<br>
Any ideas to workaround/fix this ?
<br>
<br>
<a class="moz-txt-link-freetext"
href="http://docs.redhat.com/docs/en-US/Red_Hat_Storage_Software_Appliance/3.2/html/User_Guide/chap-Administration_Guide-GlusterFS_Client.html">http://docs.redhat.com/docs/en-US/Red_Hat_Storage_Software_Appliance/3.2/html/User_Guide/chap-Administration_Guide-GlusterFS_Client.html</a>
<br>
<br>
ENVIRONMENT:
<br>
OS: RHEL6 x86_64
<br>
GlusterFS: 3.2.5
<br>
Windows OS: Windows2008R2
<br>
Windows NFS ver: NFSv3
<br>
<br>
We tried to solve this problem with Microsoft.
<br>
We captured network traffic between NFS server and NFS client.
<br>
Access call is sent to NFS server from NFS client before sending
delete call.
<br>
We found that glusterfs has returnd 'not allow (ACCESS3_DELETE=0)'
to the access call.
<br>
In the case that glusterfs is connected to linux via NFS, linux
NFS client is deleting files and directories by ignoring 'not
allow (ACCESS3_DELETE=0)'.
<br>
However, windows NFS client does not ignore 'not allow
(ACCESS3_DELETE=0)' and does not try to files and directories.
<br>
<br>
Our research summary:
<br>
NFS server NFS client responce to access call
<br>
gluster NFS server　<->　windows NFS client Not Allow Delete
(can't delete any files and directories)
<br>
gluster NFS server <->　linux NFS client Not Allow Delete
(can delete files and directories by ignoring responce to access
call)
<br>
linux NFS server <->　windows NFS client Allow Delete (can
delete files and directories)
<br>
<br>
We took captures of network traffic on three cases.
<br>
Summary of the captures to access call are below for reference.
<br>
<br>
--Captures (gluster NFS server<-> windows NFS client)--
<br>
No. Time Source
SourcePort Destination DestPort Protocol Info
<br>
1079 2011-12-22 19:39:37.586504 10.129.0.145
946 10.129.0.60 38467 NFS V3 ACCESS Call
(Reply In 1080), FH:0xc306b6b5
<br>
Network File System, ACCESS Call FH:0xc306b6b5
<br>
[Program Version: 3]
<br>
[V3 Procedure: ACCESS (4)]
<br>
object
<br>
access: 0x10
<br>
.... .0 = not allow READ
<br>
.... 0. = not allow LOOKUP
<br>
...0 .. = not allow MODIFY
<br>
..0. .. = not allow EXTEND
<br>
.1.. .. = allow DELETE
<br>
0... .. = not allow EXECUTE
<br>
<br>
No. Time Source
SourcePort Destination DestPort Protocol Info
<br>
1080 2011-12-22 19:39:37.587195 10.129.0.60
38467 10.129.0.145 946 NFS V3 ACCESS Reply
(Call In 1079)
<br>
Network File System, ACCESS Reply
<br>
[Program Version: 3]
<br>
[V3 Procedure: ACCESS (4)]
<br>
Status: NFS3_OK (0)
<br>
obj_attributes
<br>
access: 0x00
<br>
.... .0 = not allow READ
<br>
.... 0. = not allow LOOKUP
<br>
...0 .. = not allow MODIFY
<br>
..0. .. = not allow EXTEND
<br>
.0.. .. = not allow DELETE
<br>
0... .. = not allow EXECUTE
<br>
---------------------------------
<br>
<br>
--Captures (gluster NFS server<-> linux NFS client)--
<br>
<br>
No. Time Source
SourcePort Destination DestPort Protocol Info
<br>
11 2011-12-27 18:58:48.628804 10.201.0.121
859 10.201.0.14 38467 NFS V3 ACCESS Call
(Reply In 12), FH:0x4aa48fe2
<br>
Network File System, ACCESS Call FH:0x4aa48fe2
<br>
[Program Version: 3]
<br>
[V3 Procedure: ACCESS (4)]
<br>
object
<br>
access: 0x1f
<br>
.... .1 = allow READ
<br>
.... 1. = allow LOOKUP
<br>
...1 .. = allow MODIFY
<br>
..1. .. = allow EXTEND
<br>
.1.. .. = allow DELETE
<br>
0... .. = not allow EXECUTE
<br>
<br>
No. Time Source
SourcePort Destination DestPort Protocol Info
<br>
12 2011-12-27 18:58:48.630107 10.201.0.14
38467 10.201.0.121 859 NFS V3 ACCESS Reply
(Call In 11)
<br>
Network File System, ACCESS Reply
<br>
[Program Version: 3]
<br>
[V3 Procedure: ACCESS (4)]
<br>
Status: NFS3_OK (0)
<br>
obj_attributes Directory mode:0755 uid:0 gid:0
<br>
access: 0x0f
<br>
.... .1 = allow READ
<br>
.... 1. = allow LOOKUP
<br>
...1 .. = allow MODIFY
<br>
..1. .. = allow EXTEND
<br>
.0.. .. = not allow DELETE
<br>
0... .. = not allow EXECUTE
<br>
-------------------------------
<br>
<br>
--Captures (linux NFS server<-> windows NFS client)--
<br>
<br>
No. Time Source
SourcePort Destination DestPort Protocol Info
<br>
11 2011-12-27 18:58:48.628804 10.201.0.121
859 10.201.0.14 38467 NFS V3 ACCESS Call
(Reply In 12), FH:0x4aa48fe2
<br>
Network File System, ACCESS Call FH:0x4aa48fe2
<br>
[Program Version: 3]
<br>
[V3 Procedure: ACCESS (4)]
<br>
object
<br>
access: 0x1f
<br>
.... .1 = allow READ
<br>
.... 1. = allow LOOKUP
<br>
...1 .. = allow MODIFY
<br>
..1. .. = allow EXTEND
<br>
.1.. .. = allow DELETE
<br>
0... .. = not allow EXECUTE
<br>
<br>
No. Time Source
SourcePort Destination DestPort Protocol Info
<br>
12 2011-12-27 18:58:48.630107 10.201.0.14
38467 10.201.0.121 859 NFS V3 ACCESS Reply
(Call In 11)
<br>
Network File System, ACCESS Reply
<br>
[Program Version: 3]
<br>
[V3 Procedure: ACCESS (4)]
<br>
Status: NFS3_OK (0)
<br>
obj_attributes Directory mode:0755 uid:0 gid:0
<br>
access: 0x0f
<br>
.... .1 = allow READ
<br>
.... 1. = allow LOOKUP
<br>
...1 .. = allow MODIFY
<br>
..1. .. = allow EXTEND
<br>
.0.. .. = not allow DELETE
<br>
0... .. = not allow EXECUTE
<br>
--------------------------------------------
<br>
<br>
<br>
<div class="moz-txt-sig"><span class="moz-txt-tag">-- <br>
</span>Kazuyuki Morita
<br>
<a class="moz-txt-link-abbreviated"
href="mailto:k.morita@ntt.com">k.morita@ntt.com</a>
<br>
<br>
</div>
</div>
</body>
</html>