All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Kryger <bobk@panix.com>
To: nfs@lists.sourceforge.net,
	For users of Fedora <fedora-list@redhat.com>,
	Bob Kryger <bobk@panix.com>
Subject: nfs write problems
Date: Tue, 02 Oct 2007 15:56:41 -0400	[thread overview]
Message-ID: <4702A279.3080001@panix.com> (raw)

So, I have a relatively new system on which I am seeing strange NFS 
behavior.

In short I am getting seemingly random errors in files written via NFS.

    * I do not get the errors if I write files locally.
    * I have no errors in the NIC, I even tried a second NIC in a PCI
      slot as opposed to the onboard one. There are no errors recorded
      on the NIC or the switch on a 1Gb port.
    * I see no memory errors, I ran memtest for 3 days clean.
    * To test I am using dd if=/dev/zero of various (large) file sizes.
    * Since I know that the file should be all zeros I wrote a C program
      to read it back and tell me where it finds non-zero bytes. The
      program results are confirmed with od.
    * The files read back always have the errors in the same place, so
      it is not a problem with reading the files.
    * There are no errors in any logs.
    * The problem occurs on both the RAID1 (ext3) and RAID10 (xfs)
      filesystems.
    * I've tried two clients, both FC5 one 64bit, and the other a 32 bit
      with the same results. This error was uncovered by users
      attempting to write files from other systems and other Fedora
      releases, so it is repeatable regardless of the client.
    * the server is not running anything else and spends a large portion
      of the time idle. loadaverages are quite low. swap is mostly
      unused. a large portion of RAM is allocated to file cache, but I
      expect that this would be normal for this amount of file IO.

The server is running an up-to-date FC6, although this also occurred 
with FC5. I am about to try F7.

Hardware is an AMD 1220 dual core 64bit, on a Tyan K8SSA S3950
with an Adaptec Raid 2230SLP and 7 Fujitsu MAU3147NC.
The RAID config is that 1 disks (on diff channels) are in a Mirror for 
the OS, 4 are in a Raid 10 config and 1 is a hot spare.

Anyone ever seen anything like this before?
Suggest where I might look next?
Additional tests?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2007-10-02 19:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02 19:56 Bob Kryger [this message]
2007-10-03  0:07 ` nfs write problems Trond Myklebust
2007-10-03 10:21   ` Bob Kryger
2007-10-03 13:31     ` J. Bruce Fields
2007-10-03 17:53       ` Bob Kryger
2007-10-04 20:12       ` [NFS] " Bob Kryger

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=4702A279.3080001@panix.com \
    --to=bobk@panix.com \
    --cc=fedora-list@redhat.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.