Tomoaki, this is very useful. I will look deeper soon.<div>Thanks!</div><div><br></div><div>Avati<br><br><div class="gmail_quote">On Thu, Jun 21, 2012 at 9:21 PM, Tomoaki Sato <span dir="ltr"><<a href="mailto:tsato@valinux.co.jp" target="_blank">tsato@valinux.co.jp</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Avati,<br>
<br>
tshark says ...<br>
FH values that the linux kernel NFS server returns stays constant for every LOOKUP 'foo' but,<br>
FH values that the GlusterFS(NFS) returns are non-constant.<br>
<br>
operaions at the ESXi host:<br>
<br>
~ # ./getcwd /vmfs/volumes/94925201-78f190e0/foo<br>
========= sleep 30 ================<br>
/vmfs/volumes/94925201-78f190e0/foo<br>
~ #<br>
<br>
tshark's output at the linux kernel NFS server:<br>
<br>
# tshark -i 2 -R nfs<br>
Running as user "root" and group "root". This could be dangerous.<br>
Capturing on br0<br>
/* chdir */<br>
2.056680 192.168.1.23 -> 192.168.1.254 NFS V3 GETATTR Call, FH:0x1ffd38ff<br>
2.056990 192.168.1.254 -> 192.168.1.23 NFS V3 GETATTR Reply (Call In 13) Directory mode:0755 uid:0 gid:0<br>
9.848666 192.168.1.23 -> 192.168.1.254 NFS V3 GETATTR Call, FH:0x1ffd38ff<br>
9.848767 192.168.1.254 -> 192.168.1.23 NFS V3 GETATTR Reply (Call In 60) Directory mode:0755 uid:0 gid:0<br>
9.848966 192.168.1.23 -> 192.168.1.254 NFS V3 LOOKUP Call, DH:0x1ffd38ff/foo<br>
9.849049 192.168.1.254 -> 192.168.1.23 NFS V3 LOOKUP Reply (Call In 62), FH:0xdb05b90a <=====<br>
20.055508 192.168.1.23 -> 192.168.1.254 NFS V3 GETATTR Call, FH:0x1ffd38ff<br>
20.055702 192.168.1.254 -> 192.168.1.23 NFS V3 GETATTR Reply (Call In 103) Directory mode:0755 uid:0 gid:0<br>
29.054939 192.168.1.23 -> 192.168.1.254 NFS V3 GETATTR Call, FH:0x1ffd38ff<br>
29.055180 192.168.1.254 -> 192.168.1.23 NFS V3 GETATTR Reply (Call In 132) Directory mode:0755 uid:0 gid:0<br>
38.054338 192.168.1.23 -> 192.168.1.254 NFS V3 GETATTR Call, FH:0x1ffd38ff<br>
38.054583 192.168.1.254 -> 192.168.1.23 NFS V3 GETATTR Reply (Call In 151) Directory mode:0755 uid:0 gid:0<br>
/* getcwd */<br>
39.849107 192.168.1.23 -> 192.168.1.254 NFS V3 LOOKUP Call, DH:0xdb05b90a/..<br>
39.849449 192.168.1.254 -> 192.168.1.23 NFS V3 LOOKUP Reply (Call In 170), FH:0x1ffd38ff<br>
39.849676 192.168.1.23 -> 192.168.1.254 NFS V3 READDIRPLUS Call, FH:0x1ffd38ff<br>
39.849833 192.168.1.254 -> 192.168.1.23 NFS V3 READDIRPLUS Reply (Call In 172) . .. foo<br>
39.850071 192.168.1.23 -> 192.168.1.254 NFS V3 LOOKUP Call, DH:0x1ffd38ff/foo<br>
39.850149 192.168.1.254 -> 192.168.1.23 NFS V3 LOOKUP Reply (Call In 174), FH:0xdb05b90a<br>
39.850746 192.168.1.23 -> 192.168.1.254 NFS V3 LOOKUP Call, DH:0xdb05b90a/..<br>
39.850814 192.168.1.254 -> 192.168.1.23 NFS V3 LOOKUP Reply (Call In 176), FH:0x1ffd38ff<br>
39.851014 192.168.1.23 -> 192.168.1.254 NFS V3 READDIRPLUS Call, FH:0x1ffd38ff<br>
39.851095 192.168.1.254 -> 192.168.1.23 NFS V3 READDIRPLUS Reply (Call In 178) . .. foo<br>
39.851329 192.168.1.23 -> 192.168.1.254 NFS V3 LOOKUP Call, DH:0x1ffd38ff/foo<br>
39.851438 192.168.1.254 -> 192.168.1.23 NFS V3 LOOKUP Reply (Call In 180), FH:0xdb05b90a <=====<br>
<br>
operations at the ESXi host:<br>
<br>
~ # ./getcwd /vmfs/volumes/ef172a87-e5ae817f/foo<br>
========= sleep 30 ================<br>
<div class="im">getcwd: No such file or directory<br>
~ #<br>
<br>
</div>tshark's output at the GlusterFS(NFS) server:<br>
<br>
# tshark -i 1 -R nfs<br>
Running as user "root" and group "root". This could be dangerous.<br>
Capturing on eth0<br>
/* chdir */<br>
1.228396 192.168.1.23 -> 192.168.1.136 NFS V3 GETATTR Call, FH:0x43976ad5<br>
1.229406 192.168.1.136 -> 192.168.1.23 NFS V3 GETATTR Reply (Call In 6) Directory mode:0755 uid:0 gid:0<br>
4.445894 192.168.1.23 -> 192.168.1.136 NFS V3 GETATTR Call, FH:0x43976ad5<br>
4.446916 192.168.1.136 -> 192.168.1.23 NFS V3 GETATTR Reply (Call In 16) Directory mode:0755 uid:0 gid:0<br>
4.447099 192.168.1.23 -> 192.168.1.136 NFS V3 LOOKUP Call, DH:0x43976ad5/foo<br>
4.448147 192.168.1.136 -> 192.168.1.23 NFS V3 LOOKUP Reply (Call In 18), FH:0x3f9fd887 <=====<br>
10.228438 192.168.1.23 -> 192.168.1.136 NFS V3 GETATTR Call, FH:0x43976ad5<br>
10.229432 192.168.1.136 -> 192.168.1.23 NFS V3 GETATTR Reply (Call In 31) Directory mode:0755 uid:0 gid:0<br>
19.228321 192.168.1.23 -> 192.168.1.136 NFS V3 GETATTR Call, FH:0x43976ad5<br>
19.229309 192.168.1.136 -> 192.168.1.23 NFS V3 GETATTR Reply (Call In 47) Directory mode:0755 uid:0 gid:0<br>
28.228139 192.168.1.23 -> 192.168.1.136 NFS V3 GETATTR Call, FH:0x43976ad5<br>
28.229112 192.168.1.136 -> 192.168.1.23 NFS V3 GETATTR Reply (Call In 70) Directory mode:0755 uid:0 gid:0<br>
/* getcwd */<br>
34.448796 192.168.1.23 -> 192.168.1.136 NFS V3 LOOKUP Call, DH:0x3f9fd887/..<br>
34.450119 192.168.1.136 -> 192.168.1.23 NFS V3 LOOKUP Reply (Call In 81), FH:0x42966b36<br>
34.450343 192.168.1.23 -> 192.168.1.136 NFS V3 READDIRPLUS Call, FH:0x42966b36<br>
34.452105 192.168.1.136 -> 192.168.1.23 NFS V3 READDIRPLUS Reply (Call In 83) .. foo .<br>
34.452311 192.168.1.23 -> 192.168.1.136 NFS V3 LOOKUP Call, DH:0x42966b36/..<br>
34.453464 192.168.1.136 -> 192.168.1.23 NFS V3 LOOKUP Reply (Call In 85), FH:0xbc1b2900<br>
34.453648 192.168.1.23 -> 192.168.1.136 NFS V3 LOOKUP Call, DH:0x42966b36/foo<br>
34.454677 192.168.1.136 -> 192.168.1.23 NFS V3 LOOKUP Reply (Call In 87), FH:0x3e9ed964 <======<br>
<br>
Regards,<br>
<br>
Tomo<br>
<div class="HOEnZb"><div class="h5"><br>
(2012年06月20日 16:28), Tomoaki Sato wrote:<br>
> Avati,<br>
><br>
> I've tried following:<br>
> 1) 'esxcfg-nas -d gluster_nfs' at the ESXi host.<br>
> 2) 'volume set bar nfs.enable-ino32 on' at the 192.168.1.136 host.<br>
> 3) 'volume stop bar' and 'volume start bar' at the 192.168.1.136 host.<br>
> 4) 'esxcfg-nas -a -o 192.168.1.136 -s /bar gluster_nfs' at the ESXi host.<br>
><br>
> on the ESXi host:<br>
><br>
> ~ # uname -m<br>
> x86_64<br>
> ~ # mkdir /vmfs/volumes/ef172a87-e5ae817f/after-enable-ino32-on<br>
> ~ # ls -liR /vmfs/volumes/ef172a87-e5ae817f<br>
> /vmfs/volumes/ef172a87-e5ae817f:<br>
> -2118204814 drwxr-xr-x 1 root root 4096 Jun 20 07:13 after-enable-ino32-on<br>
> 1205893126 drwxr-xr-x 1 root root 4096 Jun 20 07:08 baz<br>
> -1291907235 drwx------ 1 root root 16384 Jun 6 23:41 lost+found<br>
><br>
> /vmfs/volumes/ef172a87-e5ae817f/after-enable-ino32-on:<br>
><br>
> /vmfs/volumes/ef172a87-e5ae817f/baz:<br>
> -1374929331 drwxr-xr-x 1 root root 4096 Jun 19 06:41 foo<br>
><br>
> /vmfs/volumes/ef172a87-e5ae817f/baz/foo:<br>
><br>
> /vmfs/volumes/ef172a87-e5ae817f/lost+found:<br>
> ~ # ./getcwd /vmfs/volumes/ef172a87-e5ae817f/after-enable-ino32-on<br>
> getcwd: No such file or directory<br>
> ~ #<br>
><br>
> on the 192.168.1.136 host:<br>
><br>
> # gluster volume info bar<br>
><br>
> Volume Name: bar<br>
> Type: Distribute<br>
> Volume ID: b2d75589-8370-4528-ab4e-b543b3abdc3b<br>
> Status: Started<br>
> Number of Bricks: 1<br>
> Transport-type: tcp<br>
> Bricks:<br>
> Brick1: bar-1-private:/mnt/brick<br>
> Options Reconfigured:<br>
> diagnostics.brick-log-level: TRACE<br>
> diagnostics.client-log-level: TRACE<br>
> nfs.enable-ino32: on<br>
><br>
> please fine attached nfs.log5.<br>
><br>
> Regards,<br>
><br>
> Tomo<br>
><br>
> (2012/06/20 16:11), Anand Avati wrote:<br>
>> -1374929331 drwxr-xr-x 1 root root 4096 Jun 19 06:41 foo<br>
>><br>
>> ...<br>
>><br>
>> 2920037965 drwxr-xr-x 2 root root 4096 Jun 19 15:41 foo<br>
>><br>
>><br>
>> Ouch!<br>
>><br>
>> -1374929331 == (int32_t) 2920037965<br>
>><br>
>> 'uname -m' from the ESXi host please! Is it a 32bit OS? Can you try 'gluster volume set bar nfs.enable-ino32 on' and retry?<br>
>><br>
>> Avati<br>
><br>
<br>
</div></div></blockquote></div><br></div>