From: Chris Penney <cpenney@gmail.com>
To: nfs@lists.sourceforge.net
Subject: NFS Corruption
Date: Tue, 29 Mar 2005 16:08:16 -0500 [thread overview]
Message-ID: <111aefd050329130844a0042e@mail.gmail.com> (raw)
Where I am we are starting to move to using Linux NFS servers now that
2.6 seems relatively stable (we need >2GB volumes) and I setup a SLES
9 with SP1 on a dual-cpu pentium4 system with 2GB ram and four 1TB san
supplied luns form an LSI array. I tried various combonations of
jfs/xfs/resiserfs (mainly I was using jfs) with lvm2/md/dm for
building a volume (as well as a plain lun) and no matter what I did I
was getting corruption (I tried smp and up kernels). Typically it
would show up as a bad md5sum of a ~2.5GB file I was copying from an
NFS client (a SuSE 9.1 system) while a couple of instances of iozone
or dbench were running. It usually required a fsck to fix and was
fairly easily repeatable. If I download 2.6.11.5 and apply NFS-ALL
and the latest DM patches everything seems fine.
Is this a known issue that was recently fixed? The bug was really
easy for me to reproduce. The main reason I'm asking is because I
really don't like to use a downloaded kernel tree with SLES 9 and I'd
like to know what needs to go in so I can watch for it and switch back
when it goes in.
Thanks,
Chris
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2005-03-29 21:08 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=111aefd050329130844a0042e@mail.gmail.com \
--to=cpenney@gmail.com \
--cc=nfs@lists.sourceforge.net \
--cc=penney@msu.edu \
/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.