From owner-freebsd-stable@FreeBSD.ORG Sun Jul 3 03:50:36 2011 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 B51ED106564A for ; Sun, 3 Jul 2011 03:50:36 +0000 (UTC) (envelope-from cscotts@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6AF558FC16 for ; Sun, 3 Jul 2011 03:50:36 +0000 (UTC) Received: by vxg33 with SMTP id 33so4250422vxg.13 for ; Sat, 02 Jul 2011 20:50:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=tZVaDOJhSxffSb6MiupggrnXBLuGkZTJ8jeeAEXedsc=; b=w4E1PluDcWDJpI6PoytVZQfhy9NyGs3niTI2iev3fqs7GFYiU8A1QRy2nKEr4qQ93d cqLgoXORI152llOeVSY/izZhMaRn0b3I7i1QqZIBTjJn7CjE9Ig/YlDfAQ8AK1U5yABg MB+3w9VWC4ts85zeAN+NeWtyMaD4P47oUOrN0= Received: by 10.220.176.3 with SMTP id bc3mr1887331vcb.26.1309665035472; Sat, 02 Jul 2011 20:50:35 -0700 (PDT) Received: from sahibkuran.kjlms (user-0c2hi2t.cable.mindspring.com [24.40.200.93]) by mx.google.com with ESMTPS id bh5sm92931vcb.27.2011.07.02.20.50.33 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 02 Jul 2011 20:50:34 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Scott Sipe In-Reply-To: <20110702045435.GA81502@DataIX.net> Date: Sat, 2 Jul 2011 23:50:32 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <54D65EC5-9A9B-4F96-BB45-1904F2147CBA@gmail.com> References: <20110701222232.GA33935@icarus.home.lan> <20110702045435.GA81502@DataIX.net> To: jhell , Jeremy Chadwick X-Mailer: Apple Mail (2.1084) Cc: freebsd-stable List Subject: Re: scp: Write Failed: Cannot allocate memory 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: Sun, 03 Jul 2011 03:50:36 -0000 On Jul 2, 2011, at 12:54 AM, jhell wrote: > On Fri, Jul 01, 2011 at 03:22:32PM -0700, Jeremy Chadwick wrote: >> On Fri, Jul 01, 2011 at 03:13:17PM -0400, Scott Sipe wrote: >>> I'm running 8.2-RELEASE and am having new problems with scp. When = scping >>> files to a ZFS directory on the FreeBSD server -- most notably large = files >>> -- the transfer frequently dies after just a few seconds. In my last = test, I >>> tried to scp an 800mb file to the FreeBSD system and the transfer = died after >>> 200mb. It completely copied the next 4 times I tried, and then died = again on >>> the next attempt. >>>=20 >>> On the client side: >>>=20 >>> "Connection to home closed by remote host. >>> lost connection" >>>=20 >>> In /var/log/auth.log: >>>=20 >>> Jul 1 14:54:42 freebsd sshd[18955]: fatal: Write failed: Cannot = allocate >>> memory >>>=20 >>> I've never seen this before and have used scp before to transfer = large files >>> without problems. This computer has been used in production for = months and >>> has a current uptime of 36 days. I have not been able to notice any = problems >>> copying files to the server via samba or netatalk, or any problems = in >>> apache. >>>=20 >>> Uname: >>>=20 >>> FreeBSD xeon 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Sat Feb 19 01:02:54 = EST >>> 2011 root@xeon:/usr/obj/usr/src/sys/GENERIC amd64 >>>=20 >>> I've attached my dmesg and output of vmstat -z. >>>=20 >>> I have not restarted the sshd daemon or rebooted the computer. >>>=20 >>> Am glad to provide any other information or test anything else. >>>=20 >>> {snip vmstat -z and dmesg} >>=20 >> You didn't provide details about your networking setup (rc.conf, >> ifconfig -a, etc.). netstat -m would be useful too. >>=20 >> Next, please see this thread circa September 2010, titled "Network >> memory allocation failures": >>=20 >> = http://lists.freebsd.org/pipermail/freebsd-stable/2010-September/thread.ht= ml#58708 >>=20 >> The user in that thread is using rsync, which relies on scp by = default. >> I believe this problem is similar, if not identical, to yours. >>=20 >=20 > Please also provide your output of ( /usr/bin/limits -a ) for the = server > end and the client. >=20 > I am not quite sure I agree with the need for ifconfig -a but some > information about the networking driver your using for the interface > would be helpful, uptime of the boxes. And configuration of the pool. > e.g. ( zpool status -a ;zfs get all ) You should probably > prop this information up somewhere so you can reference by URL = whenever > needed. >=20 > rsync(1) does not rely on scp(1) whatsoever but rsync(1) can be made = to > use ssh(1) instead of rsh(1) and I believe that is what Jeremy is > stating here but correct me if I am wrong. It does use ssh(1) by > default. >=20 > Its a possiblity as well that if using tmpfs(5) or mdmfs(8) for /tmp > type filesystems that rsync(1) may be just filling up your temp ram = area > and causing the connection abort which would be expected. ( df -h ) = would > help here. Hello, I'm not using tmpfs/mdmfs at all. The clients yesterday were 3 different = OSX computers (over gigabit). The FreeBSD server has 12gb of ram and no = bce adapter. For what it's worth, the server is backed up remotely every = night with rsync (remote FreeBSD uses rsync to pull) to an offsite (slow = cable connection) FreeBSD computer, and I have not seen any errors in = the nightly rsync. Sorry for the omission of networking info, here's the output of the = requested commands and some that popped up in the other thread: http://www.cap-press.com/misc/ In rc.conf: ifconfig_em1=3D"inet 10.1.1.1 netmask 255.255.0.0" Scott