From owner-freebsd-arm@freebsd.org Sat Sep 5 04:09:32 2015 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 974859CAEEE for ; Sat, 5 Sep 2015 04:09:32 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (kientzle.com [142.254.26.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 504EE1319 for ; Sat, 5 Sep 2015 04:09:31 +0000 (UTC) (envelope-from tim@kientzle.com) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id t853eNeb024181 for freebsd-arm@freebsd.org; Sat, 5 Sep 2015 03:40:23 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.108] (192.168.1.101 [192.168.1.101]) by kientzle.com with SMTP id g88pd5re9t7fk4c74rd4v423n2; for freebsd-arm@freebsd.org; Sat, 05 Sep 2015 03:40:23 +0000 (UTC) (envelope-from tim@kientzle.com) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: very odd behaviour from svnlite on RPi2 From: Tim Kientzle In-Reply-To: <20150904223214.GA80713@potato.growveg.org> Date: Fri, 4 Sep 2015 20:40:17 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <644A3890-CEF7-4ED4-BB85-616C09EE1E6F@kientzle.com> References: <20150904173804.GA82922@potato.growveg.org> <46ddeb2caa6.2d9e5c4c@mail.schwarzes.net> <20150904223214.GA80713@potato.growveg.org> To: freebsd-arm X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Sep 2015 04:09:32 -0000 > On Sep 4, 2015, at 3:32 PM, John = wrote: >=20 > On Fri, Sep 04, 2015 at 11:33:54PM +0200, Andreas Schwarz wrote: >=20 >> I got this svn errors from time to time, independently from the rpi. = For=20 >> getting and updating the ports tree, you can also use the "portsnap" = tool >> (it's part of the base system). >=20 > Yeah I thought about doing this instead of svnlite (after I'd started = svnlite). > After 10 restarts I got so annoyed I made a while loop. I've never = used=20 > portsnap because I thought it lagged behind svn, but I might use it in = future,=20 > maybe it's suited more to low-power systems. Svn should work just fine on "low power systems," but has had problems = on FreeBSD-based RPi and BeagleBone for a long time. I suspect the root cause is a bug in SVN when dealing with extremely = slow disk: I think the TCP connection times out while the svn client is = doing a long series of disk operations. It certainly should not be happening. > I've not seen these errors on the other freebsd boxes in the logs = (same=20 > connection) which is why I thought it might be a bottleneck with the = pi. In some cases, I've repeated the 'svn cleanup' + 'svn up' cycle for 2-3 = days before it finally completed only to see missing files that svn = doesn't seem to be aware of at all. I've found that partial tree = checkouts are more likely to succeed; you can sometimes work around this = by asking SVN to checkout/update individual subdirectories. For FreeBSD source checkouts, I recommend using git which doesn't seem = to suffer from this problem. Similarly, portsnap is more resilient than = svn for ports checkouts. Tim