From owner-freebsd-current@FreeBSD.ORG Tue Oct 15 13:37:10 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1A3B8341 for ; Tue, 15 Oct 2013 13:37:10 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id EAEA92431 for ; Tue, 15 Oct 2013 13:37:09 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 87E453C317 for ; Tue, 15 Oct 2013 13:37:06 +0000 (UTC) Message-ID: <525D451F.3040005@allanjude.com> Date: Tue, 15 Oct 2013 09:37:35 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: vmstat -z: zfs related failures on r255173 References: <1381521443.74219922.8eyuscyw@frv45.ukr.net> <1381837350.494453682.d94z37mg@frv45.ukr.net> In-Reply-To: <1381837350.494453682.d94z37mg@frv45.ukr.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Oct 2013 13:37:10 -0000 On 2013-10-15 07:53, Dmitriy Makarov wrote: > Please, any idea, thougth, help! > Maybe what information can be useful for diggin - anything... > > System what I'm talkin about has a huge problem: performance degradation in short time period (day-two). Don't know can we somehow relate this vmstat fails with degradation. > > > >> Hi all >> >> On CURRENT r255173 we have some interesting values from vmstat -z : REQ = FAIL >> >> [server]# vmstat -z >> ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP >> ....... skipped.... >> NCLNODE: 528, 0, 0, 0, 0, 0, 0 >> space_seg_cache: 64, 0, 289198, 299554,25932081,25932081, 0 >> zio_cache: 944, 0, 37512, 50124,1638254119,1638254119, 0 >> zio_link_cache: 48, 0, 50955, 38104,1306418638,1306418638, 0 >> sa_cache: 80, 0, 63694, 56, 198643,198643, 0 >> dnode_t: 864, 0, 128813, 3, 184863,184863, 0 >> dmu_buf_impl_t: 224, 0, 1610024, 314631,157119686,157119686, 0 >> arc_buf_hdr_t: 216, 0,82949975, 56107,156352659,156352659, 0 >> arc_buf_t: 72, 0, 1586866, 314374,158076670,158076670, 0 >> zil_lwb_cache: 192, 0, 6354, 7526, 2486242,2486242, 0 >> zfs_znode_cache: 368, 0, 63694, 16, 198643,198643, 0 >> ..... skipped ...... >> >> Can anybody explain this strange failures in zfs related parameters in vmstat, can we do something with this and is this really bad signal? >> >> Thanks! > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" I am guessing those 'failures' are failures to allocate memory. I'd recommend you install sysutils/zfs-stats and send the list the output of 'zfs-stats -a' -- Allan Jude