From owner-freebsd-stable@FreeBSD.ORG Mon Apr 25 15:38:15 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EB3416A4CE for ; Mon, 25 Apr 2005 15:38:15 +0000 (GMT) Received: from mx1.uni-c.dk (mx1.uni-c.dk [130.228.5.194]) by mx1.FreeBSD.org (Postfix) with SMTP id 78FA243D5E for ; Mon, 25 Apr 2005 15:38:13 +0000 (GMT) (envelope-from Rasmus.Brogger@uni-c.dk) Received: (qmail 14469 invoked by uid 64014); 25 Apr 2005 15:38:03 -0000 Received: from Rasmus.Brogger@uni-c.dk by mx1 by uid 64011 with qmail-scanner-1.22 (uvscan: v4.1.60/v4294. avp: 4.0.3.0. Clear:RC:1(80.211.231.119):. Processed in 2.06886 secs); 25 Apr 2005 15:38:03 -0000 Received: from p-119.vpn-snet.uni-c.dk (HELO ?80.211.231.119?) (80.211.231.119) by mx1.uni-c.dk with SMTP; 25 Apr 2005 15:38:00 -0000 Message-ID: <426D0EDF.50500@uni-c.dk> Date: Mon, 25 Apr 2005 17:38:07 +0200 From: =?ISO-8859-1?Q?Rasmus_Br=F8gger?= User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <426BA8FA.3080602@samsco.org> <426C85EA.5090906@speechpro.com> In-Reply-To: <426C85EA.5090906@speechpro.com> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: background_fsck=no does not work? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Apr 2005 15:38:15 -0000 Igor Robul wrote: > Palle Girgensohn wrote: > >> >> No, but the machine crashes a lot, sometimes a couple of times in a >> day (oddly mostly on week-ends, and sometimes it can be stable for a >> week or two). I'm clueless to what's causing it, but suspect that the >> amd64 stuff is broken, at least for this machine (dual Xeon). I wanted >> foreground fsck since I thought there might be a problem with the file >> systems, but I guess I was wrong... >> > I had frequent panics which I tracked to time I had started rsync (with > large data) over em0 gigabit netcard. > I have reinserted card and it works fine now, so I think this was > "conductor problem". > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" I run quite a lot of rsync of large archives, and I've had no problems at all. System is a 5.3-RELEASE-p2 on a Dell 1750 (Dual Xeon 2.8 with 2GB ram), not em but bge gigabit driver. The system peaks with about 150 connected rsync sessions, the archive to sync is about 90GB and some 200k files. The netload ranges between 10 mbit/s to 180 mbit/s. At peaks it hits a load about 30. I've done very little tuning, but the disk system runs via a Qlogic HBA to gain faster IO from a SAN. Only problem I've had was when about 130 rsync clients connecting within the same second. It saturated the server for some 10 min. at a load above 150, it didn't crash however and recoverd slowly. This was fixed by changing the dial-up schedule on the clients. 5.3 is indeed very stable :) Cheers, Rasmus