LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 01-05-2008, 05:22 PM   #1
zkab
Member
 
Registered: Dec 2007
Posts: 142

Rep: Reputation: 16
NFS stalls


I have Ubuntu 7.10 computers in my network and 2 computers are set up as NFS servers.
Very often when I copy (cp) large files from NFS client to NFS server the client stalls ... same thing when I from the client copy large files between NFS servers.

What should I check to solve this problem ... BTW I have a couple of Windows XP computers in the network also and Windows do not have any problem to copy much larger files to the NFS servers (they act as Samba servers also)

I had the feeling that Linux was superior to Windows but ... I mean NFS has been around for ages so it should be rock-solid ...
 
Old 01-05-2008, 05:26 PM   #2
Brian1
LQ Guru
 
Registered: Jan 2003
Location: Seymour, Indiana
Distribution: Distribution: RHEL 5 with Pieces of this and that. Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700

Rep: Reputation: 65
Try using async as an option in your /etc/exports file.
If no luck post info in /etc/exports file.

Brian
 
Old 01-06-2008, 06:10 AM   #3
zkab
Member
 
Registered: Dec 2007
Posts: 142

Original Poster
Rep: Reputation: 16
When I read the NFS documentation I got the impression that sync was the recommended option for NFS2/3 due to the risk of possible data corruption ... it says:

'Finally, note that, for NFS version 3 protocol requests, a subsequent commit request from the NFS client at file close time, or at fsync() time, will force the server to write any previously unwritten data/metadata to the disk, and the server will not reply to the client until this has been completed, as long as sync behavior is followed. If async is used, the commit is essentially a no-op, since the server once again lies to the client, telling the client that the data has been sent to stable storage. This again exposes the client and server to data corruption, since cached data may be discarded on the client due to its belief that the server now has the data maintained in stable storage.'

My /etc/exports looks like:

/my_media_lib 192.168.1.44(rw,subtree_check,sync)

On my NFS-client (the one who dies) cat /var/log/messages | grep nfs gives:

Jan 6 04:45:09 pluto kernel: [16403.378139] nfs: server neptun not responding, still trying

And on my NFS server /var/log/messages gives:

Jan 6 06:14:03 neptun -- MARK --
Jan 6 06:34:03 neptun -- MARK --
Jan 6 06:54:03 neptun -- MARK --
Jan 6 07:14:03 neptun -- MARK --
Jan 6 07:34:03 neptun -- MARK --
Jan 6 07:36:20 neptun syslogd 1.4.1#21ubuntu3: restart.
Jan 6 07:54:03 neptun -- MARK --
Jan 6 08:14:03 neptun -- MARK --

How to interpret these messages ... why doesn't server respond ?
If you need more output please let me know.
I will test your recommendation with async and let you know how it went ...
 
Old 01-06-2008, 11:55 AM   #4
Brian1
LQ Guru
 
Registered: Jan 2003
Location: Seymour, Indiana
Distribution: Distribution: RHEL 5 with Pieces of this and that. Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700

Rep: Reputation: 65
Have you tried changing sync to async and see if the issue still continues. No idea on errors posted.

Brian
 
Old 01-06-2008, 01:24 PM   #5
zkab
Member
 
Registered: Dec 2007
Posts: 142

Original Poster
Rep: Reputation: 16
OK - I will test it
 
Old 01-08-2008, 08:44 AM   #6
zkab
Member
 
Registered: Dec 2007
Posts: 142

Original Poster
Rep: Reputation: 16
It WORKS !!! Thanks for solution.
I have tested it with several large files between NFS servers and client. The CPU utilization is high but the client survives.

One question though ... since the only thing I changed is sync -> async in /etc/exports for the NFS servers it must imply that everything else is set-up OK for my NFS servers/clients. How come the default/recommended option sync doesn't work for NFSv3 ... is it a bug ?
 
Old 01-08-2008, 03:44 PM   #7
Brian1
LQ Guru
 
Registered: Jan 2003
Location: Seymour, Indiana
Distribution: Distribution: RHEL 5 with Pieces of this and that. Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700

Rep: Reputation: 65
I don't really know an answer to that unless googling but have no time for that. async just pretty much starts transferring and does not really confirm it is complete like the sync option. async is much faster to transfer files than sync.

Brian
 
Old 01-08-2008, 03:50 PM   #8
zkab
Member
 
Registered: Dec 2007
Posts: 142

Original Poster
Rep: Reputation: 16
OK ... I will google and see what I can find
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
GRUB stalls dave111 Linux - Software 8 07-13-2006 11:17 AM
Firefox stalls? corbintechboy Debian 2 01-23-2006 04:39 PM
knoppix stalls drum2jc Linux - Laptop and Netbook 10 08-11-2004 01:01 PM
RH 7.3 Stalls install itgl72 Linux - Newbie 4 05-14-2003 12:21 AM
x11 stalls ChimpFace9000 Linux - Software 1 05-07-2003 09:24 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 05:12 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration