From owner-freebsd-stable@FreeBSD.ORG Tue Mar 13 21:19:31 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C835B1065674 for ; Tue, 13 Mar 2012 21:19:31 +0000 (UTC) (envelope-from regnauld@x0.dk) Received: from moof.catpipe.net (moof.catpipe.net [194.28.252.64]) by mx1.freebsd.org (Postfix) with ESMTP id 84E198FC08 for ; Tue, 13 Mar 2012 21:19:30 +0000 (UTC) Received: from localhost (moof.catpipe.net [194.28.252.64]) by localhost.catpipe.net (Postfix) with ESMTP id ED5DA4CEDEB; Tue, 13 Mar 2012 22:19:28 +0100 (CET) Received: from moof.catpipe.net ([194.28.252.64]) by localhost (moof.catpipe.net [194.28.252.64]) (amavisd-new, port 10024) with ESMTP id 0AUUhzmd0zoS; Tue, 13 Mar 2012 22:19:28 +0100 (CET) Received: from macbook.bluepipe.net (x0.dk [194.19.205.214]) (Authenticated sender: relayuser) by moof.catpipe.net (Postfix) with ESMTPA id 9DD494CEDA7; Tue, 13 Mar 2012 22:19:28 +0100 (CET) Received: by macbook.bluepipe.net (Postfix, from userid 1001) id 57AFE84F87F; Tue, 13 Mar 2012 22:19:28 +0100 (CET) Date: Tue, 13 Mar 2012 22:19:28 +0100 From: Phil Regnauld To: Mikolaj Golub Message-ID: <20120313211928.GJ25709@macbook.bluepipe.net> References: <20120311185457.GB1684@macbook.bluepipe.net> <861uoyvpzh.fsf@kopusha.home.net> <20120311220911.GD1684@macbook.bluepipe.net> <20120312143127.GM12975@macbook.bluepipe.net> <86k42pu0tb.fsf@kopusha.home.net> <20120312232223.GG12975@macbook.bluepipe.net> <86fwdcw7tm.fsf@kopusha.home.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86fwdcw7tm.fsf@kopusha.home.net> X-Operating-System: Darwin 11.3.0 x86_64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: Issue with hast replication X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2012 21:19:31 -0000 Mikolaj Golub (to.my.trociny) writes: > > Ok. So it is send(2). I suppose the network driver could generate the > error. Did you tell what network adaptor you had? Not yet. bce0: mem 0xf4000000-0xf5ffffff irq 16 at device 0.0 on pci2 bce0: ASIC (0x57092003); Rev (C0); Bus (PCIe x2, 2.5Gbps); B/C (4.6.4); Bufs (RX:2;TX:2;PG:8); Flags (SPLT|MSI|MFW); MFW (NCSI 1.0.3) > PR> No obvious errors there either, but again what should I look out for ? > > I would look at sysctl -a dev. statistics and try to find if there is correlation > between ENOMEM failures and growing of error counters. 0 errors: dev.bce.0.l2fhdr_error_count: 0 dev.bce.0.stat_emac_tx_stat_dot3statsinternalmactransmiterrors: 0 dev.bce.0.stat_Dot3StatsCarrierSenseErrors: 0 dev.bce.0.stat_Dot3StatsFCSErrors: 0 dev.bce.0.stat_Dot3StatsAlignmentErrors: 0 > Looking at buffer usage from 'netstat -nax' output ran during synchronization > (on both hosts) could provide useful info where the bottleneck is. top -HS > output might be useful too. Good point. I'll have to attempt to recreate the problem, as the volume has replicated without errors. Typical. Cheers, Phil