From: Steve Dickson <SteveD@redhat.com>
To: Dan McNulty <dan.mcnulty@eckoh.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Unable to copy large files to NFS server
Date: Mon, 31 Jul 2006 12:43:15 -0400 [thread overview]
Message-ID: <44CE3323.3080502@RedHat.com> (raw)
In-Reply-To: <E092A2FD32592642884987B611E09A09024BAB@ukth008-2kaex-t.eckoh.com>
Dan McNulty wrote:
> Hi,
> =
> =
> =
> We have recently purchased a new EMC NAS solution. I have successfully =
> configured our newer (Fedora4) servers to access this successfully.
> =
> =
> =
> However we have a number of RedHat 7.2 servers (kernel 2.4.18), which I =
> have successfully mounted to the Server, and can copy small files OK. =
> However, when I try to copy larger files to the Server, the system just =
> hangs, and then the mount becomes unusable; I=92m unable to kill the hung =
> process and cannot unmount. I have tried to edit the rsize/wsize options =
> but this hasn=92t worked. The current entry in /etc/fstab looks like this:
> =
> =
> =
> Servername:/path1/path2/Production /mnt/Production nfs =
> rsize=3D4096,wsize=3D4096,nfsvers=3D3 0 0
> =
> =
> =
> In /var/log/messages I see lots of these errors:
> =
> =
> =
> Jul 31 16:29:51 client1 kernel: nfs: server Servername not responding, =
> still trying
> =
> Jul 31 16:31:40 client1 kernel: nfs: task 189 can't get a request slot
> =
> Jul 31 16:31:40 client1 kernel: nfs: task 190 can't get a request slot
> =
> =
> =
> The main problem is that I can write small files and it works OK. As =
> soon as I try to transfer a larger file, the client writes a 0 byte file =
> to the server (with the correct filename) then just hangs. I then can=92t =
> do anything with the mount. Any help on what I should be looking at =
> would be much appreciated!
Are you using UDP or TCP mounts? If udp, switch to TCP.. also,
use 'tethereal -w /tmp/data.pcap host <server>' to capture this
hang to see which side stop sending (meaning is the client waiting
for a reply or is the server waiting for another request).
I know in the past, EMC server had an issue with how FC and RHEL kernels
handled ESTALE messages... but I doubt that is happening in this
case... but you might want to rummage around in both bug database
(assuming you have access to EMC's) and see if this a known issue and
if there is a fix to it..
steved.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2006-07-31 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 16:20 Unable to copy large files to NFS server Dan McNulty
2006-07-31 16:43 ` Steve Dickson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44CE3323.3080502@RedHat.com \
--to=steved@redhat.com \
--cc=dan.mcnulty@eckoh.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.