All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lisa Williams" <lisa@fastclick.com>
To: <nfs@lists.sourceforge.net>
Subject: Data Corruption Issues
Date: Wed, 27 Aug 2003 10:51:44 -0700	[thread overview]
Message-ID: <008601c36cc3$e1ae87c0$d501010a@Lisa> (raw)

Hi all,

We are finding corruption in mysql database files that are being copied from
16 Linux 2.4.20 servers to a Linux 2.4.21 backup server on an hourly basis.

Here are the details:

The backup server was originally a FreeBSD box that was having some hardware
issues.  We decided to swap it out and replace with a Linux server (running
2.4.21).  We had no issues of data corruption until we swapped machines.

The 16 linux 2.4.20 servers have the backup machine mounted locally and
after each hour a script is run that flushes the tables and then copies them
to the mounted backup drive.  There's no real pattern of which machines
create a corrupt file on the backup machine.  It appears fairly random.  We
are seeing about 20% of them corrupted.

Our network is running at 100MB.

The files are around 25MB each.

We have tried the following settings:

    Increasing the number of nfsd server threads to 20 on the backup
machine.

Changes in the mount options in the 16 fstabs:

    specifying:  tcp, nfsvers=3
    specifying:  udp, nfsvers=2
    specifying:  rsize=1024,wsize=1024

There was no real change in the corruption rate after any of these changes.

Any ideas of what we should try next are appreciated.

Thank you,

-Lisa



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2003-08-27 17:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='008601c36cc3$e1ae87c0$d501010a@Lisa' \
    --to=lisa@fastclick.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.