Re: performance/writebehind behavior

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jul 28, 2014 at 10:43 AM, Richard van der Hoff <richard@xxxxxxxxxxxxxx> wrote:
On 28/07/14 18:05, Anand Avati wrote:
Whether flush-behind is enabled or not, close() will guarantee all
previous write()s on that fd have been acknowledged by server.

Thanks Anand. So can you explain why the 'wc' in my example doesn't see all of the data written by the dd?


I'm wondering if it is because of attribute cache. Maybe attribute cache (either in fuse or gluster, don't know yet) is not getting invalidated for some reason. Try each of the following and check if any of them make the test work right:

#1 mount glusterfs with --attribute-cache=0

#2 disable stat prefetch with : gluster volume set $name performance.stat-prefetch off


That should help diagnose the problem further.

Thanks

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux