[SATLUG] Copying 5+GBs over wifi to another system
bartonekdragracing at yahoo.com
Thu Feb 14 16:55:34 CST 2013
Fixing to do a thorough test.
I have a spare WRT54G wired/wireless router laying around and some sort of newish Dell desktop. Going to install Linux Mint 14 and Solaris 10 on this box, setup a NFS share.
The new box will be wired direct to the WRT54G and I will use my laptop to transfer a few GB's wirelessly to both Linux and Unix to see if it is a OS issue. Then I will hook up wired and retry.
I'll report back on what I find out. Time to solve this nagging problem.
--- On Thu, 2/14/13, Frank Huddleston <fhuddles at gmail.com> wrote:
From: Frank Huddleston <fhuddles at gmail.com>
Subject: Re: [SATLUG] Copying 5+GBs over wifi to another system
To: satlug at satlug.org
Date: Thursday, February 14, 2013, 3:08 PM
I use only NFS on my home LAN, and I think I've copied Gigbytes over WiFi. I can't remember exactly when and how much, and while I've had problems with my Wifi, they don't seem to involve NFS particularly.
I'm currently running Debian Squeeze on my systems. I would not think that the distribution would matter much, but maybe.
Are you saying that you see ca. 3.5% CPU in top on the NFS server? Which process? Is this during the transfer?
I note that on my server I've got two files for services in the startup directory (/etc/init.d): nfs-common and nfs-kernel-server. I don't know the difference: I'm just mentioning it.
I am trying a transfer now, to test, and I see, on the server, nfsd shows, like, 0% cpu in top. It does show up in the display, though. So 3% sounds like a lot.
Have you tried these transfers using ethernet-cable connected clients? That would remove the wireless connection and help you to know if it's a wireless issue or an NFS issue.
SATLUG mailing list
SATLUG at satlug.org
http://alamo.satlug.org/mailman/listinfo/satlug to manage/unsubscribe
Powered by Rackspace (www.rackspace.com)
More information about the SATLUG