From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: patl@curl.com (Patrick J. LoPresti)
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [NFS] Help: 2.2.18 NFS is corrupting our files
Date: 22 Jan 2001 19:57:46 +0100 [thread overview]
Message-ID: <shsbsszqus5.fsf@charged.uio.no> (raw)
In-Reply-To: <s5gvgr71xao.fsf@egghead.curl.com>
In-Reply-To: patl@curl.com's message of "22 Jan 2001 09:22:39 -0500"
>>>>> " " == Patrick J LoPresti <patl@curl.com> writes:
> This developer is now regularly seeing two problems which began
> with the 2.2.18 upgrade. First, remote clients occasionally
> get "stale NFS file handle" errors for no apparent reason.
> Second, some of the files are being corrupted.
What filesystem are you exporting?
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2001-01-22 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s5gvgr71xao.fsf@egghead.curl.com>
2001-01-22 18:57 ` Trond Myklebust [this message]
2001-01-22 19:41 ` [NFS] Help: 2.2.18 NFS is corrupting our files Patrick J. LoPresti
2001-01-23 9:07 ` Neil Brown
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=shsbsszqus5.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=patl@curl.com \
/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