glusterfs.git -

	Commit message (Collapse)	Author	Age	Files	Lines
*	disperse: mark bug-1236065.t as bad_test	Niels de Vos	2016-05-02	1	-0/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	tests/bugs/disperse/bug-1236065.t failed several times on different Jenkins slaves: * https://build.gluster.org/job/rackspace-regression-2GB-triggered/20316/console * https://build.gluster.org/job/rackspace-regression-2GB-triggered/20320/console * https://build.gluster.org/job/rackspace-regression-2GB-triggered/20321/console BUG: 1332054 Change-Id: Ie1934f09f843c2089c187e9295288c16c01913d2 Signed-off-by: Niels de Vos <ndevos@redhat.com> Reviewed-on: http://review.gluster.org/14138 Reviewed-by: Susant Palai <spalai@redhat.com> Smoke: Gluster Build System <jenkins@build.gluster.com> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org> Reviewed-by: Vijay Bellur <vbellur@redhat.com> CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
*	cluster/ec: Fix tracking of good bricks	Xavier Hernandez	2015-08-06	1	-0/+95
	The bitmask of good and bad bricks was kept in the context of the corresponding inode or fd. This was problematic when an external process (another client or the self-heal process) did heal the bricks but no one changed the bitmaks of other clients. This patch removes the bitmask stored in the context and calculates which bricks are healthy after locking them and doing the initial xattrop. After that, it's updated using the result of each fop. Change-Id: I225e31cd219a12af4ca58871d8a4bb6f742b223c BUG: 1236065 Signed-off-by: Xavier Hernandez <xhernandez@datalab.es> Reviewed-on: http://review.gluster.org/11844 Tested-by: NetBSD Build System <jenkins@build.gluster.org> Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>