Date: Wed, 27 Aug 2008 16:57:54 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: Weldon S Godfrey 3 <weldon@excelsus.com> Cc: freebsd-fs@freebsd.org, pjd@freebsd.org Subject: Re: ZFS-NFS kernel panic under load Message-ID: <Pine.GSO.4.63.0808271647170.27228@muncher.cs.uoguelph.ca> In-Reply-To: <20080827161150.G76650@emmett.excelsus.com> References: <20080806101621.H24586@emmett.excelsus.com> <20080814091337.Y94482@emmett.excelsus.com> <20080821153107.W76650@emmett.excelsus.com> <20080821194742.GA19362@eos.sc1.parodius.com> <20080822115932.M76650@emmett.excelsus.com> <20080822174411.GA89610@eos.sc1.parodius.com> <20080827161150.G76650@emmett.excelsus.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 27 Aug 2008, Weldon S Godfrey 3 wrote:
>
> Well, I am not sure if it was exactly that bug, since the last time I
> paniced, it never dumped to memory. Although this time i paniced, it started
> to dump then locked up solid.
>
> before I paniced I did get an error message at the end of the panic:
>
>
> Stopped at nfsrv_access at 0x190 testb 0x1, 0xa4 (%rax)
>
Well, I'd guess that is the following source line:
if (rdonly || (vp->v_mount->mnt_flag & MNT_RDONLY)) {
since "mnt_flag" is way down in the structure and MNT_RDONLY == 0x1.
This suggests that v_mount is no longer valid, but I have no idea why that
might happen. (This was looking at the -current nfsserver sources, but I
don't think they've changed much.
Maybe someone who knows ZFS and how it handles the mount structure might
have some idea?
rick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.0808271647170.27228>