|Will on 25 May 2013 22:08:36 -0700|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|Re: [PLUG] Raspberry Pi NAS questions, cont'd|
I would just say use a different device for the NAS like a cubie board or beagle bone black. The reason being is that the pi (and other ARM v6 processors depending on the vendor) use the USB bus for the Ethernet controller.
That said, I have not had an issue with my pi using rsync. Granted I am running arch on my pi which could be the reason.
In case anyone's not familiar w/the idea of a Raspberry Pi NAS, it uses a very small- as in credit card sized- ARM PC running a Debian distro, plus 2 USB hard drives. You set up the shares via Samba, and then mirror them on a regular basis using rsync.
So, I've got 1/2 of the Raspberry Pi NAS set up. Specifically, I've got the shares working. Woo. Unfortunately, the rsync part isn't working. Not the command format- that's easy. The problem is w/the USB drives themselves. Both drives share the same USB 2.0 bus, and while that's faster than 1.0, it's hardly screaming. And, in this case, it appears that, when rsync (or cp) try to push too many bits across the bus, the Pi simply drops both connections and cancels the whole copy.
I've tried throttling the connection via the --bwlimit command, but even bringing it to 10 kb/s (which is ridiculously slow) causes the copy to bomb at times. Any ideas about how I could make the Raspbian/Pi/rsync combo work a bit better?
And, yes, I'm Googling this too...
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug