NFS write corruption on 8.0-RELEASE

[Bernd Walter]

On Fri, Feb 12, 2010 at 04:08:55PM -0800, alan bryan wrote:
> 
> 
> --- On Fri, 2/12/10, Rick Macklem <rmacklem at uoguelph.ca> wrote:
> 
> > From: Rick Macklem <rmacklem at uoguelph.ca>
> > Subject: Re: NFS write corruption on 8.0-RELEASE
> > To: "Dmitry Marakasov" <amdmi3 at amdmi3.ru>
> > Cc: freebsd-hackers at freebsd.org, freebsd-stable at freebsd.org, "John Baldwin" <jhb at freebsd.org>
> > Date: Friday, February 12, 2010, 11:12 AM
> > 
> > 
> > On Fri, 12 Feb 2010, Dmitry Marakasov wrote:
> > 
> > >
> > > I'm planning a massive testing for this weekend,
> > including removing
> > > soft mount option and trying linux client/server.
> > >
> > > Btw, I forgot to mention that I'm experiencing other
> > NFS problems from
> > > time to time, including "death" of a mount (that is,
> > all processes that
> > > try to access it freeze; this cures itself in some
> > time with a message
> > > "server is alive again"). Also I've seen another
> > strange thing - not
> > > only the mount dies but the network is flooded with
> > NFS traffic.
> > > Last time I've seen it quite a while ago, so I don't
> > remember the
> > > circumstances and direction of the traffic.
> > >
> > There are some patches at:
> >      http://people.freebsd.org/~rmacklem
> > that may be relevant if you are using vanilla FreeBSD-8.0.
> > (They're all
> > now in stable/8, but are post-release of 8.0.)
> > 
> > rick
> > 
> > _______________________________________________
> > freebsd-stable at freebsd.org
> > mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
> > 
> 
> 
> This is interesting:
> 
> "I've seen another strange thing - not only the mount dies but the network is flooded with NFS traffic."

You might be able to see NFS flooding with:
Write file on client.
rm the file during the write on the server.
The client now gets IO-errors, but keeps trying forever.
Maybe it depends on the mechanism the client application uses to write
the file.
I never reported because my client is an old 7.0-stable system.
I originally noticed it when downloading files with seamonkey on my
client and mv it on the server to another partition before it was
completely downloaded.

-- 
B.Walter <bernd at bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.