From: David Rees <dbr@greenhydrant.com>
To: nfs@lists.sourceforge.net
Subject: Known NFS Read corruption in recent kernels with NFS_ALL?
Date: Fri, 18 Oct 2002 16:25:44 -0700 [thread overview]
Message-ID: <20021018162544.A18218@greenhydrant.com> (raw)
I had been running 2.4.18 with NFS_ALL for quite some time with out any
problems on a number of machines running as both client and server using
nfsv3 and default mount options.
However, after upgrading a server to 2.4.19 with NFS_ALL (the old NFS_ALL
patch, not the one dated 5 Oct) I started noticing what seemed like random
read corruption from 2.4.18-NFS_ALL and 2.4.19-NFS_ALL clients. From what I
can tell, the client is caching data from the server in some weird way and
never goes back to the server to actually verify the data, but this is just
a guess.
Is this a known issue? If so, does the latest NFS_ALL patch solve this
issue or should I stay back at 2.4.18-NFS_ALL?
Thanks,
Dave
-------------------------------------------------------
This sf.net email is sponsored by:
Access Your PC Securely with GoToMyPC. Try Free Now
https://www.gotomypc.com/s/OSND/DD
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2002-10-18 23:25 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=20021018162544.A18218@greenhydrant.com \
--to=dbr@greenhydrant.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.