Date: Fri, 12 Apr 2013 12:56:10 +0000 From: "Eggert, Lars" <lars@netapp.com> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: current <current@freebsd.org> Subject: Re: newnfs pkgng database corruption? Message-ID: <8A9F25C5-C5E6-4373-85F9-C47642CF1BAE@netapp.com> In-Reply-To: <746529932.761884.1365721847968.JavaMail.root@erie.cs.uoguelph.ca> References: <746529932.761884.1365721847968.JavaMail.root@erie.cs.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Apr 12, 2013, at 1:10, Rick Macklem <rmacklem@uoguelph.ca> wrote: > Well, I have no idea why an NFS server would reply errno 70 if the file > still exists, unless the client has somehow sent a bogus file handle > to the server. (I am not aware of any client bug that might do that. I > am almost suspicious that there might be a memory problem or something > that corrupts bits in the network layer. Do you have TSO enabled for your > network interface by any chance? If so, I'd try disabling that on the > network interface. Same goes for checksum offload.) >=20 > rick > ps: If you can capture packets between the client and server at the > time this error occurs, looking at them in wireshark might be > useful? I will try all of those things. But first, a question that someone who understands pkgng will be able to an= swerr: Is this "fake-pkg" process even running on the NFS mount? The WRKDIR= is /tmp, which is an mfs mount. Lars=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8A9F25C5-C5E6-4373-85F9-C47642CF1BAE>