Date: Sun, 25 Jan 2009 14:26:10 -0500 (EST) From: Rick Macklem <rmacklem@uoguelph.ca> To: Dmitry Marakasov <amdmi3@amdmi3.ru> Cc: freebsd-current@freebsd.org Subject: Re: NFS data corruption Message-ID: <Pine.GSO.4.63.0901251422120.16653@muncher.cs.uoguelph.ca> In-Reply-To: <20090123221826.GB30982@deprived.panopticon> References: <20090123221826.GB30982@deprived.panopticon>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 24 Jan 2009, Dmitry Marakasov wrote:
[stuff about data corruption snipped]
>
> Is there any way I can help to diagnose and fix the problem?
>
> Here's amd.map file which is used to mount this filesystem:
>
> ---
> /defaults type:=nfs;rhost:=hive;opts:=rw,nosuid,noexec,-3,-i,-s,-T
> * rfs:=/pool/${key}
> ---
>
A couple of simple things you could try:
1 - rebuild your kernel with "option NFS_LEGACYRPC" and try that.
2 - try it without the "-s" option (since nothing reports a failure,
is seems unlikely that an RPC would have timed out, but maybe the
app. doesn't check for error returns on write. In general, I consider
"soft" mounts to be a bad idea, but that's just imho.)
Good luck with it, rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.0901251422120.16653>