From owner-freebsd-fs@FreeBSD.ORG Thu Jun 13 07:57:47 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3D2C2F43 for ; Thu, 13 Jun 2013 07:57:47 +0000 (UTC) (envelope-from Ivailo.Tanusheff@skrill.com) Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe002.messaging.microsoft.com [216.32.181.182]) by mx1.freebsd.org (Postfix) with ESMTP id E43CD1E47 for ; Thu, 13 Jun 2013 07:57:46 +0000 (UTC) Received: from mail161-ch1-R.bigfish.com (10.43.68.231) by CH1EHSOBE018.bigfish.com (10.43.70.68) with Microsoft SMTP Server id 14.1.225.23; Thu, 13 Jun 2013 07:42:30 +0000 Received: from mail161-ch1 (localhost [127.0.0.1]) by mail161-ch1-R.bigfish.com (Postfix) with ESMTP id 929231C01BD; Thu, 13 Jun 2013 07:42:30 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -1 X-BigFish: PS-1(z54eehz9371I542I4015Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz17326ah8275dhz2fh2a8h668h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh9a9j1155h) Received-SPF: pass (mail161-ch1: domain of skrill.com designates 157.56.249.213 as permitted sender) client-ip=157.56.249.213; envelope-from=Ivailo.Tanusheff@skrill.com; helo=AM2PRD0710HT004.eurprd07.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:SKI; SFS:; DIR:OUT; SFP:; SCL:-1; SRVR:DB3PR07MB057; H:DB3PR07MB059.eurprd07.prod.outlook.com; LANG:en; Received: from mail161-ch1 (localhost.localdomain [127.0.0.1]) by mail161-ch1 (MessageSwitch) id 1371109347953425_25617; Thu, 13 Jun 2013 07:42:27 +0000 (UTC) Received: from CH1EHSMHS035.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.242]) by mail161-ch1.bigfish.com (Postfix) with ESMTP id DAD6420004D; Thu, 13 Jun 2013 07:42:27 +0000 (UTC) Received: from AM2PRD0710HT004.eurprd07.prod.outlook.com (157.56.249.213) by CH1EHSMHS035.bigfish.com (10.43.70.35) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 13 Jun 2013 07:42:27 +0000 Received: from DB3PR07MB057.eurprd07.prod.outlook.com (10.242.137.144) by AM2PRD0710HT004.eurprd07.prod.outlook.com (10.255.165.39) with Microsoft SMTP Server (TLS) id 14.16.324.0; Thu, 13 Jun 2013 07:42:12 +0000 Received: from DB3PR07MB059.eurprd07.prod.outlook.com (10.242.137.149) by DB3PR07MB057.eurprd07.prod.outlook.com (10.242.137.144) with Microsoft SMTP Server (TLS) id 15.0.702.21; Thu, 13 Jun 2013 07:42:11 +0000 Received: from DB3PR07MB059.eurprd07.prod.outlook.com ([169.254.2.14]) by DB3PR07MB059.eurprd07.prod.outlook.com ([169.254.2.14]) with mapi id 15.00.0702.005; Thu, 13 Jun 2013 07:42:11 +0000 From: Ivailo Tanusheff To: Jona Schuman , "freebsd-fs@freebsd.org" Subject: RE: zfs send/recv dies when transferring large-ish dataset Thread-Topic: zfs send/recv dies when transferring large-ish dataset Thread-Index: AQHOZ8ZVUN+hFJBhLk6aHw9omdejRZkzQxIg Date: Thu, 13 Jun 2013 07:42:11 +0000 Message-ID: <57e0551229684b69bc27476b8a08fb91@DB3PR07MB059.eurprd07.prod.outlook.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [217.18.249.148] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: skrill.com X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jun 2013 07:57:47 -0000 Hi, Can you try send/recv with the -v or with -vP swiches, so you can see more = verbose information? Regards, Ivailo Tanusheff -----Original Message----- From: owner-freebsd-fs@freebsd.org [mailto:owner-freebsd-fs@freebsd.org] On= Behalf Of Jona Schuman Sent: Thursday, June 13, 2013 2:41 AM To: freebsd-fs@freebsd.org Subject: zfs send/recv dies when transferring large-ish dataset Hi, I'm getting some strange behavior from zfs send/recv and I'm hoping someone= may be able to provide some insight. I have two identical machines running= 9.0-RELEASE-p3, each having a ZFS pool (zfs 5, zpool 28) for storage. I want to use zfs send/recv for replication between the tw= o machines. For the most part, this has worked as expected. However, send/recv fails when transferring the largest dataset (both in act= ual size and in terms of number of files) on either machine. With these datasets, issuing: machine2# nc -d -l 9999 | zfs recv -d storagepool machine1# zfs send datase= t@snap | nc machine2 9999 terminates early on the sending side without any error messages. The receiv= ing end continues on as expected, cleaning up the partial data received so = far and reverting to its initial state. (I've tried using mbuffer instead o= f nc, or just using ssh, both with similar results.) Oddly, zfs send dies s= lightly differently depending on how the two machines are connected. When c= onnected through the racktop switch, zfs send dies quietly without any indi= cation that the transfer has failed. When connected directly using a crossover cable, zfs send dies quietly and = machine1 becomes unresponsive (no network, no keyboard, hard reset required= ). In both cases, no messages are printed to screen or to anything in /var/= log/. I can transfer the same datasets successfully if I send/recv to/from file: machine1# zfs send dataset@snap > /tmp/dump machine1# scp /tmp/dump machine= 2:/tmp/dump machine2# zfs recv -d storagepool < /tmp/dump so I don't think the datasets themselves are the issue. I've also successfu= lly tried send/recv over the network using different network interfaces (10= GbE ixgbe cards instead of the 1GbE igb links), which would suggest the iss= ue is with the 1GbE links. Might there be some buffering parameter that I'm neglecting to tune, which = is essential on the 1GbE links but may be less important on the faster link= s? Are there any known issues with the igb driver that might be the culprit= here? Any other suggestions? Thanks, Jona _______________________________________________ freebsd-fs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-fs To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"