glusterfs.git -

	Commit message (Collapse)	Author	Age	Files	Lines
*	features/shard: Fix shard inode refcount when it's part of priv->lru_list.	Krutika Dhananjay	2018-03-02	1	-17/+0
\| \| \| \| \| \| \| \| \| \| \|	For as long as a shard's inode is in priv->lru_list, it should have a non-zero ref-count. This patch achieves it by taking a ref on the inode when it is added to lru list. When it's time for the inode to be evicted from the lru list, a corresponding unref is done. Change-Id: I289ffb41e7be5df7489c989bc1bbf53377433c86 BUG: 1468483 Signed-off-by: Krutika Dhananjay <kdhananj@redhat.com>
*	tests/basic/inode-leak.t: mark as known issue	Amar Tumballi	2017-11-27	1	-0/+7
\| \| \| \| \| \| \| \| \| \| \| \|	Mainly because the tests are consistently taking more than 20mins for each runs. One of the samples from a regression run: > /tests/basic/inode-leak.t - 1643 second Change-Id: If11572203c702f64847794f6d578a6dc19a0dee8 Signed-off-by: Amar Tumballi <amarts@redhat.com>
*	tests : add a test to check if there is an inode leak	Mohamed Ashiq Liyazudeen	2017-11-22	1	-0/+41
	This test check if there is inode leak in bricks. lru_size for mount is expected to be zero. active_size for mount is expected to be 1 which is of root. Change-Id: I18762b4255af411f1b55c0be98451c8ef1b35478 BUG: 1370116 Signed-off-by: Mohamed Ashiq Liyazudeen <mliyazud@redhat.com>