On Thu, 4 Mar 2010, Daniel Braniss wrote:
correct. The interesting side effect, is that I can't see any negative
issues when disabling the cash.
If the client retries a non-idempotent RPC, the server will do it
again, which can result in data corruption. This is likely to happen
infrequentl
>
>
> On Wed, 3 Mar 2010, Daniel Braniss wrote:
>
> > disabling the krpc reply cache does it, no visible damage. Somehow
> > this reminds me of my old 1970 beetle, parts would fall off but it would
> > continue working :-)
> > where to go from here?
> >
> Ok, so it sounds like the leak is in the
On Wed, 3 Mar 2010, Daniel Braniss wrote:
disabling the krpc reply cache does it, no visible damage. Somehow
this reminds me of my old 1970 beetle, parts would fall off but it would
continue working :-)
where to go from here?
Ok, so it sounds like the leak is in the krpc reply cache code, if
>
>
> On Tue, 2 Mar 2010, Daniel Braniss wrote:
>
> > runing with the experimental nfs server all is ok!
> > (at least I can't see any mbuf leakage :-)
> >
> > so now that we can assume that the problem is in NFS/UDP writes via
> > classic nfsserver, where to look?
> >
>
> It might also be the
On Sun, 28 Feb 2010 16:52:44 +0200 Daniel Braniss
wrote about Re: mbuf leakage with nfs/udp (was: mbuf leakage with nfs/zfs):
DB> well, I have further reduced the problem, it happens with NFS/UDP
DB> writes. i'll try the wireshark road, but i'm very rusty with RPC, the
DB> oth
On Feb 28, 2010, at 2:52 PM, Daniel Braniss wrote:
> well, I have further reduced the problem, it happens with NFS/UDP writes.
> i'll try the wireshark road, but i'm very rusty with RPC, the other road is to
> check the changes, my oldest is from late october (RC2) where it's happening,
> while
>
> On Feb 28, 2010, at 12:11 PM, Daniel Braniss wrote:
>
> >> I'm pulling in Robert Watson, who has some familiarity with the UDP
> >> stack/code in FreeBSD. I'm not sure he'll be a sufficient source of
> >> knowledge for this specific issue since it appears (?) to be specific =to
> >> NFS; Rick