Re: newnfs pkgng database corruption?

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.)
> 
> 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 answerr: Is this "fake-pkg" process even running on the NFS mount? The WRKDIR is /tmp, which is an mfs mount.

Lars
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"