Re: NetBSD's read-subvol-entry.t spurious failures explained

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

 



On Fri, Mar 06, 2015 at 05:55:34PM +0530, Ravishankar N wrote:
> >On NetBSD I can see that AFR never gets trusted.afr.patchy-client-0
> >and walways things brick0 is fine. AFR randomly picks brick0 or brick1
> >to list directory content, and when it picks brick0 the test fails.
> After bringing brick0 up, and performing "ls abc/def", does afr_do_readdir()
> get called for "def"?

Yes, it is. 

> If it does,  then AFR will send lookup to both bricks via
> afr_inode_refresh() ,

How is it supposed to happen? I can see I do not get into 
afr_inode_refresh_do() after visiting afr_do_readdir().

-- 
Emmanuel Dreyfus
manu@xxxxxxxxxx
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel




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

  Powered by Linux