Date: Thu, 7 May 2009 23:59:44 -0400 From: Alexander Kabaev <kabaev@gmail.com> To: Ben Kelly <ben@wanderview.com> Cc: Richard Todd <rmtodd@ichotolot.servalan.com>, freebsd-current@freebsd.org Subject: Re: Panic: wrong vnode type 0xffffff009b7719c0 on yesterday's current. Message-ID: <8e5ef5f70905072059u51dcdbe8nd5b66f6fb5c124e4@mail.gmail.com> In-Reply-To: <619B386D-9FF5-4296-BB83-245881CA9C41@wanderview.com> References: <20090506234631.231A5CD8@mx1.synetsystems.com> <619B386D-9FF5-4296-BB83-245881CA9C41@wanderview.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On May 6, 2009, at 6:54 PM, Richard Todd wrote: > It looks like this KASSERT was added relatively recently as part of the > dotdot changes to the namecache: > > =A0http://svn.freebsd.org/viewvc/base?view=3Drevision&revision=3D190945 > > Perhaps there is further fallout from the changes that only occur with ZF= S? > > - Ben Up to recently dotdot caching in VFS was quite broken and did pay any attention to vnode types FSes did feed to it. >From backtrace and analysis provided by original poster it is evident that ZFS is trying to cache_enter(VDIR, "..", VLNK), which cannot possibly make any sense. kib@ has recently committed fixes to FFS to avoid races with vnodes being reused from under ffs_lookup, and I would not be surprised if ZFS was broken is similar fashion. --=20 Alexander Kabaev
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8e5ef5f70905072059u51dcdbe8nd5b66f6fb5c124e4>