Date: Fri, 13 Nov 1998 20:02:26 -0500 (EST) From: Simon Shapiro <shimon@simon-shapiro.org> To: Mike Smith <mike@smith.net.au> Cc: freebsd-current@FreeBSD.ORG, Andrew Gallatin <gallatin@cs.duke.edu> Subject: Re: nfs_rename() panic Message-ID: <XFMail.981113200226.shimon@simon-shapiro.org> In-Reply-To: <199811132253.OAA00889@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Mike Smith, On 13-Nov-98 you wrote: > > > > I'm getting a 100% reproducible panic in nfs_rename. This is on a > > system with sources cvsupped this morning about 10am EST. NFS is > > compiled in statically, not an LKM. The new access caching stuff is > > off. This panic does not happen in a kernel built from 1 week old > > sources. > > > > The panic happens when trn renames .newsrc in a filesystem mounted via > > NFSv3/tcp from a Solaris 2.5 server. > > > > I've appended a partial stack trace. The problem seems to be that > > fvp->v_data is somehow becoming NULL. > > Weird. I can't work out why the nfsnode would have been revoked at > that point, but it looks like it must have. There are some other bugs > in the code though, as tvp may be NULL if it was open and has been > sillyrenamed. I'll add some sanity checking, but it would be useful if > you could check that it's definitely fvp->v_data that's NULL. I am getting essentially the same result on nickel (alpha) using nomis (i386) as NFS server. Any make activity does that. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.981113200226.shimon>