Matt Benjamin wrote:
> Hi David,
>
> That sounds like a sensible plan. I mentioned this to Rick Macklem at
> this spring's NFSv4 bakeathon. Rick said he would be happy to answer
> questions and the like, to assist interested NetBSD developers who
> might be interested in taking this on.
>
The cod
> looks like, again, a race with the vnode cache.
Anything I can aid debugging this?
On Thu, Jun 20, 2013 at 04:16:23PM +0200, Edgar Fuß wrote:
> This happened on my 6.1/amd64 NFS server:
>
> uvm_fault(0xfe8419d06490, 0x0, 1) -> e
> fatal page fault in supervisor mode
> trap type 6 code 0 rip 803fa3d1 cs 8 rflags 10246 cr2 c8 cpl 0 rsp
> ff fe811db1e660
> kernel: pag
Hi David,
That sounds like a sensible plan. I mentioned this to Rick Macklem at this
spring's NFSv4 bakeathon. Rick said he would be happy to answer questions and
the like, to assist interested NetBSD developers who might be interested in
taking this on.
Matt
- "David Holland" wrote:
This happened on my 6.1/amd64 NFS server:
uvm_fault(0xfe8419d06490, 0x0, 1) -> e
fatal page fault in supervisor mode
trap type 6 code 0 rip 803fa3d1 cs 8 rflags 10246 cr2 c8 cpl 0 rsp ff
fe811db1e660
kernel: page fault trap, code=0
stopped in pid 430.2 (nfsd) at netbsd:ufs_fhtovp+0x
On Mon, Jun 17, 2013 at 06:48:23PM +0200, J. Hannken-Illjes wrote:
> > 1. Rename v_mount, which is the filesystem the vnode is on (almost
> > always / for device vnodes), to "v_myfs".
>
> What is wrong with this name? `v_mount' is the `struct mount' this
> vnode resides on and I don't se
