Palle Girgensohn wrote:
I had frequent panics which I tracked to time I had started rsync (with large data) over em0 gigabit netcard.
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 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 "[EMAIL PROTECTED]"
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 _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
