Hi Nux, If you see the same behavior with I/O done through fuse clients through, then could you please provide the glusterd(management daemon)? Also what version of glusterfs are you running? With regards, Shishir ----- Original Message ----- From: "Nux!" <nux at li.nux.ro> To: "Vijay Bellur" <vbellur at redhat.com> Cc: "Shishir Gowda" <sgowda at redhat.com>, "Gluster Users" <gluster-users at gluster.org> Sent: Wednesday, September 18, 2013 11:21:21 PM Subject: Re: gluster volume top issue On 18.09.2013 18:32, Vijay Bellur wrote: > On 09/18/2013 03:05 PM, Nux! wrote: >> On 18.09.2013 04:39, Shishir Gowda wrote: >>> Hi Nux, >>> >>> I am trying to see if the issue of "0" open fd is based on the >>> work-load, or a bug. >>> >>> Could you check top command output of "read/write" operation too? >> >> Shishir, >> >> Those commands only output the bricks and nothing more: >> >> [root at 2216 ~]# gluster volume top xenvms read nfs >> NFS Server : localhost >> NFS Server : 1726.stocare.domeniu.net >> NFS Server : 1613.stocare.domeniu.net >> NFS Server : 1631.stocare.domeniu.net >> >> [root at 2216 ~]# gluster volume top xenvms write nfs >> NFS Server : localhost >> NFS Server : 1631.stocare.domeniu.net >> NFS Server : 1613.stocare.domeniu.net >> NFS Server : 1726.stocare.domeniu.net >> >> Same without "nfs". >> > > Is this behavior observed with nfs based access only? Can you check > if the behavior remains same for fuse access too? > > -Vijay Vijay, Same with fuse. It just returns the bricks and that's it. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
