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, rickReceived on Sun Jan 25 2009 - 18:50:03 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:41 UTC