[svlug] help transfering data over 1394 cable
Mark Weisler
mark at weisler-saratoga-ca.us
Tue May 6 18:45:44 PDT 2008
On Tuesday 06 May 2008 15:04:39 Christian Einfeldt wrote:
> hi
>
> On Tue, May 6, 2008 at 2:33 PM, Scott Hess <scott at doubleu.com> wrote:
> > If you're only getting 700kbps over your subnet, you're probably doing
> > something very wrong in the first place.
>
> No surprises there. :-/
>
> > You don't indicate what kind
> > of network you have,
>
> Cat 5 cable and a Netgear en108tp:
>
> http://kbserver.netgear.com/products/EN108TP.asp
>
> > but if it's 100mbit Ethernet, you should be
> > getting ~10 megabytes/second. If you can saturate that, it would take
> > perhaps a day and a half to transfer the full 1.5T. While that's a
> > long time, it's probably faster than getting a firewire network
> > working if you're starting from scratch! Maybe you're somehow going
> > through a wireless node or something?
>
> Not likely. I have cat 5 directly to the netgear device above from both
> machines.
>
> > I'd just run rsync between them and leave it alone for awhile,
> > monitoring by running df or du periodically on the target.
>
> Sorry to ask a stupid question, but what are the commands there? Just
>
> $ rysnc
>
> and
>
> $ df
>
> and
>
> $ du
>
> > Later,
> > check in and run rsync again - this time it should be much faster.
>
> Can you please tell me a little more? What does rsync do? It seems
> remarkable that a command as simple as
>
> $ rysnc
>
> could solve my problems, but I am willing to believe it. I just don't want
> to overlook the obvious, which I often do.
>
> > You might want to tweak things to use rsyncd rather than ssh, or to
> > use blowfish or some other more efficient encryption - but if the
> > boxes are 6 months old, their CPUs might be fast enough to saturate
> > the network with no tweaking at all.
>
> yeah, AMD 3800 on the rb and 4200 on the tbb, AKFAIK. You can find the
> output of lshw for the tbb lshw here:
>
> http://www.archive.org/details/LshwForTbb
>
> You can find the output for the rb lshw here:
>
> http://www.archive.org/details/LshwForRb
>
> > You might try plugging a crossover Ethernet cable directly between the
> > boxes to make sure nothing else is screwing your networking up.
>
> I can get a crossover cable and be back here at my office within 4 hours.
> If you don't mind letting me know what I should do when the xover cable is
> in place, that would be great. Please bear in mind that i have only one
> ethernet jack on each machine, so I would need to be off of the Internet
> while deploying this diagnostic tool.
>
> > If
> > you're lucky, you'll find that both boxes can do gigabit Ethernet, and
> > everything will go faster. Don't know if you can snag a crossover
> > cable at Fry's or not.
>
> Got one at the school.
>
> > Having a 16T box implies that it's perhaps got 1T drives? You might
> > be better off just pulling one of those drives and using a sneakernet
> > to copy things over.
>
> Not really a tenable solution, because I need to move lots and lots of data
> back and forth frequently. Thanks for the thought, though!
Hi Christian,
You've gotten a lot of good advice here in this thread. And you've got a lot
invested in your media content. I recommend giving yourself some system
administration strengthening by acquiring and then going through "Running
Linux", Fifth Edition
By Matthias Kalle Dalheimer, Matt Welsh, et al
Fifth Edition December 2005
Pages: 972
ISBN 10: 0-596-00760-4 | ISBN 13: 9780596007607 by O'Reilly.
It will teach you about ssh, rsync and much more in an efficient manner. (The
man pages are not so friendly for learning purposes-but essential for
reference after one has learned the command or tool.) Working your way
through it you would learn more about security so that you can distinguish,
for example, when to use rcp and when to use rsync.
Also, with your access to recycled gear, make a learning platform, or two,
where you can try things without endangering your production environment and
data.
Viel Erfolg mit Ihre Projekte!
Mark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.svlug.org/archives/svlug/attachments/20080506/7283cb77/attachment-0001.bin
More information about the svlug
mailing list