From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
jgmtfia Mr <jgmtfia@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: NFS data corruption
Date: Thu, 13 Apr 2006 17:45:25 -0400 [thread overview]
Message-ID: <20060413214525.GC19673@fieldses.org> (raw)
In-Reply-To: <20060413185859.GA30387@ti64.telemetry-investments.com>
On Thu, Apr 13, 2006 at 02:58:59PM -0400, Bill Rugolsky Jr. wrote:
> On Wed, Apr 12, 2006 at 11:27:27PM -0400, Trond Myklebust wrote:
> > On Wed, 2006-04-12 at 21:25 -0600, jgmtfia Mr wrote:
> > > When transferring from a 2.6.16 nfs client to a 2.6.16.1 server I get
> > > data corruption. There is no indication of any problems in any log on
> > > the client or server. It does *not* happen when transferring from
> > > server to client.
> >
> > Do you get corruption with 2.6.17-rc1? That has a fix for a known
> > corruption issue.
>
> Trond,
>
> Could you point out the particular commit, or the patch from your patch
> series?
>
> [On Tuesday, I tried linux-2.6.16-NFS_ALL on a host that is re-exporting
> a NetApp NFS mount via Samba, and I got thousands of file locks that
> weren't released, so I had to discard NFS_ALL for now, until I have time
> to look closer.]
There was a problem with locks not being unlocked which has been fixed
in the latest 2.6.17-rc1 NFS_ALL.
--b.
prev parent reply other threads:[~2006-04-13 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 3:25 PROBLEM: NFS data corruption jgmtfia Mr
2006-04-13 3:27 ` Trond Myklebust
2006-04-13 18:58 ` Bill Rugolsky Jr.
2006-04-13 21:45 ` J. Bruce Fields [this message]
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=20060413214525.GC19673@fieldses.org \
--to=bfields@fieldses.org \
--cc=brugolsky@telemetry-investments.com \
--cc=jgmtfia@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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