Date: Fri, 14 Jun 2013 07:04:10 +0000 From: Ivailo Tanusheff <Ivailo.Tanusheff@skrill.com> To: Jona Schuman <jonaschuman@gmail.com>, abhay trivedi <abhaytrivedi3@gmail.com>, "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: RE: zfs send/recv dies when transferring large-ish dataset Message-ID: <97ca7eedc13f4b2b809945d067a732b6@DBXPR07MB064.eurprd07.prod.outlook.com> In-Reply-To: <CAC-LZTb4w2S2wrb3tXJsvC73h6ky_w_iPPhoeOWAsoZ-sd0Chw@mail.gmail.com> References: <CAC-LZTYLzFPTvA6S4CN0xTd-E_x9c3kxYwQoFed5LkVBrwVk0Q@mail.gmail.com> <57e0551229684b69bc27476b8a08fb91@DB3PR07MB059.eurprd07.prod.outlook.com> <CAC-LZTajW0SO_dH9ZtUH80zX628vcosL_vOzwkwB1JF1PZy0qA@mail.gmail.com> <CAL2e%2Bnek5GqWUJTJDe0pbWia%2BsY2QgSJWe_6XieGPmdX8KGjZg@mail.gmail.com> <CAC-LZTb4w2S2wrb3tXJsvC73h6ky_w_iPPhoeOWAsoZ-sd0Chw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This sounds to me as a communicational problem or system getting out of mem= ory ... -----Original Message----- From: owner-freebsd-fs@freebsd.org [mailto:owner-freebsd-fs@freebsd.org] On= Behalf Of Jona Schuman Sent: Friday, June 14, 2013 12:52 AM To: abhay trivedi; freebsd-fs@freebsd.org Subject: Re: zfs send/recv dies when transferring large-ish dataset atime is off on both origin and destination datasets On Thu, Jun 13, 2013 at 5:30 PM, abhay trivedi <abhaytrivedi3@gmail.com> wr= ote: > Can you set atime off on Destination file system and try again? > > > > On Thu, Jun 13, 2013 at 9:26 PM, Jona Schuman <jonaschuman@gmail.com> wro= te: >> >> machine2# nc -d -l 9999 | zfs receive -v -F -d storagepool machine1#=20 >> zfs send -v -R dataset@snap | nc machine2 9999 >> >> machine1-output: sending from @ to dataset@snap >> machine2-output: receiving full stream of dataset@snap into=20 >> storagepool/dataset@snap >> machine1-output: warning: cannot send 'dataset@snap': Broken pipe >> machine1-output: Broken pipe >> >> >> On Thu, Jun 13, 2013 at 3:42 AM, Ivailo Tanusheff=20 >> <Ivailo.Tanusheff@skrill.com> wrote: >> > Hi, >> > >> > Can you try send/recv with the -v or with -vP swiches, so you can=20 >> > see more verbose information? >> > >> > Regards, >> > Ivailo Tanusheff >> > >> > -----Original Message----- >> > From: owner-freebsd-fs@freebsd.org=20 >> > [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=20 >> > someone may be able to provide some insight. I have two identical=20 >> > machines running 9.0-RELEASE-p3, each having a ZFS pool (zfs 5,=20 >> > zpool >> > 28) for storage. I want to use zfs send/recv for replication=20 >> > between the two machines. For the most part, this has worked as expect= ed. >> > However, send/recv fails when transferring the largest dataset=20 >> > (both in actual size and in terms of number of files) on either machin= e. >> > With these datasets, issuing: >> > >> > machine2# nc -d -l 9999 | zfs recv -d storagepool machine1# zfs=20 >> > send dataset@snap | nc machine2 9999 >> > >> > terminates early on the sending side without any error messages.=20 >> > The receiving end continues on as expected, cleaning up the partial=20 >> > data received so far and reverting to its initial state. (I've=20 >> > tried using mbuffer instead of nc, or just using ssh, both with=20 >> > similar results.) Oddly, zfs send dies slightly differently=20 >> > depending on how the two machines are connected. When connected=20 >> > through the racktop switch, zfs send dies quietly without any indicati= on that the transfer has failed. >> > When connected directly using a crossover cable, zfs send dies=20 >> > quietly and machine1 becomes unresponsive (no network, no keyboard,=20 >> > hard reset required). In both cases, no messages are printed to=20 >> > screen or to anything in /var/log/. >> > >> > >> > I can transfer the same datasets successfully if I send/recv=20 >> > to/from >> > file: >> > >> > machine1# zfs send dataset@snap > /tmp/dump machine1# scp /tmp/dump=20 >> > machine2:/tmp/dump machine2# zfs recv -d storagepool < /tmp/dump >> > >> > so I don't think the datasets themselves are the issue. I've also=20 >> > successfully tried send/recv over the network using different=20 >> > network interfaces (10GbE ixgbe cards instead of the 1GbE igb=20 >> > links), which would suggest the issue is with the 1GbE links. >> > >> > Might there be some buffering parameter that I'm neglecting to=20 >> > tune, which is essential on the 1GbE links but may be less=20 >> > important on the faster links? Are there any known issues with the=20 >> > igb driver that might be the culprit here? Any other suggestions? >> > >> > Thanks, >> > Jona >> > _______________________________________________ >> > freebsd-fs@freebsd.org mailing list=20 >> > http://lists.freebsd.org/mailman/listinfo/freebsd-fs >> > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >> > >> > >> _______________________________________________ >> 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" > > > > > -- > T@J _______________________________________________ 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?97ca7eedc13f4b2b809945d067a732b6>