So, I use an open-source backup system called Bacula. Last night, I labelled the four brand-new 170m tapes that arrived yesterday afternoon and started full backups for the first time in nine months. All the clients went smoothly except for vorlon, my Athlon46/PCI-Express übergamebox, which would run for five seconds to a minute before the connection dropped.
Fifteen hours later, I've found the culprit. vorlon's motherboard has two onboard gigabit NICs, one an nForce NIC built into its nForce4 chipset, the other a Marvell Yukon 88E8053 PCI-E NIC. Just as an experiment, after perusing megabytes of debugging logs from the storage daemon, I tried switching vorlon's Ethernet connection from the nVidia NIC to the Marvell NIC and .... poof! Problem vanished, just like that.
vorlon is now happily streaming data across the network to babylon5 as fast as babylon5's VXA-1 tape drive can write it to tape. Clearly, there's something subtly wrong with the nForce NIC, but I don't know yet whether it's at the hardware, firmware or driver level. So, I guess I'm just not going to use it any more.
It'll be interesting if this change turns out to fix vorlon's intermittent random-lockup problem too.
Now it just remains to build and install bacula clients on yama and nijo.