mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "F. Baker" <baker@deslab.mit.edu>
To: linux-kernel@vger.kernel.org
Subject: nfs errors with xfs filesystem (2.4.x kernel)
Date: Mon, 29 Mar 2004 15:51:09 -0500	[thread overview]
Message-ID: <200403292051.i2TKp9dd027008@deslab.mit.edu> (raw)


We have several Linux x86 workstations here.  In "dmesg" on
these PCs I see a lot of errors that read:

NFS: Server wrote less than requested.

 AND

eth0: TX underrun, threshold adjusted.

This message appears whenever someone logged into the
Mandrake/RH/whatever box (with NFS autofs mounting in his/her home
directory) tries to write something to an nfs-mounted directory
(usually the home directory).  Even small files of 1.5 MB or so often
generate something such as "I/O error" when saving a file (really 
small files usually get saved fine).  And the home directory is always
based in an SGI (O2, Indy, Onyx) with xfs file system. 

Intra-SGI these transfer take place perfectly, but
Mandrake/RH/OtherLinux generates these problems.

Has anyone seen this error before and does anyone know how 
to get around it?  The kernel used is 2.4.22-28 for most
of the Mandrake boxes, or at least 2.4.x anyway.  We have not
gone to 2.6.x yet.

Thanks in advance.

baker@deslab.mit.edu

PS: Interestingly:

	cp file1 file2
where file1 is sufficiently large (1 MB or bigger) always fails the 
first time, but often does a partial write.  

If you then delete file2 and try the command anew, it works fine.
Very strange indeed.


             reply	other threads:[~2004-03-29 20:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-29 20:51 F. Baker [this message]
2004-03-30  0:57 ` Trond Myklebust

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=200403292051.i2TKp9dd027008@deslab.mit.edu \
    --to=baker@deslab.mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®