I seem to have bad luck.. Looks like an access() panic''d my system while doing a cvs checkout:> ::statusdebugging crash dump vmcore.2 (32-bit) from yamano operating system: 5.11 snv29:brandz:2 (i86pc) panic message: vn_rele: vnode ref count 0 dump content: kernel pages only> ::stackvpanic(3, fea76f38) vn_rele+0x5f(c8573b04) lo_lookup+0x497(d0811640, d221dcf0, d221de44, d221dec0, 0, c636dc40) fop_lookup+0x2f(d0811640, d221dcf0, d221de44, d221dec0, 0, c636dc40) lookuppnvp+0x2c8(d221dec0, 0, 1, 0, d221df78, c636dc40) lookuppnat+0xea(d221dec0, 0, 1, 0, d221df78, 0) lookupnameat+0x54() lookupname+0x1c(86e1990, 0, 1, 0, d221df78) access+0x8a() sys_sysenter+0x1a3() I can provide the dump, if anyone is interested. -- Eric Enright
On 1/14/06, Eric Enright <eric.enright at gmail.com> wrote:> I seem to have bad luck.. > > Looks like an access() panic''d my system while doing a cvs checkout: > > > ::status > debugging crash dump vmcore.2 (32-bit) from yamano > operating system: 5.11 snv29:brandz:2 (i86pc) > panic message: vn_rele: vnode ref count 0 > dump content: kernel pages only > > ::stack > vpanic(3, fea76f38) > vn_rele+0x5f(c8573b04) > lo_lookup+0x497(d0811640, d221dcf0, d221de44, d221dec0, 0, c636dc40) > fop_lookup+0x2f(d0811640, d221dcf0, d221de44, d221dec0, 0, c636dc40) > lookuppnvp+0x2c8(d221dec0, 0, 1, 0, d221df78, c636dc40) > lookuppnat+0xea(d221dec0, 0, 1, 0, d221df78, 0) > lookupnameat+0x54() > lookupname+0x1c(86e1990, 0, 1, 0, d221df78) > access+0x8a() > sys_sysenter+0x1a3() > > > I can provide the dump, if anyone is interested.I forgot to mention, this is reproducible. It happens every time I do a cvs checkout with netbeans 5rc1. -- Eric Enright
>On 1/14/06, Eric Enright <eric.enright at gmail.com> wrote: >> I seem to have bad luck.. >> >> Looks like an access() panic''d my system while doing a cvs checkout: >> >> > ::status >> debugging crash dump vmcore.2 (32-bit) from yamano >> operating system: 5.11 snv29:brandz:2 (i86pc) >> panic message: vn_rele: vnode ref count 0 >> dump content: kernel pages only >> > ::stack >> vpanic(3, fea76f38) >> vn_rele+0x5f(c8573b04) >> lo_lookup+0x497(d0811640, d221dcf0, d221de44, d221dec0, 0, c636dc40) >> fop_lookup+0x2f(d0811640, d221dcf0, d221de44, d221dec0, 0, c636dc40) >> lookuppnvp+0x2c8(d221dec0, 0, 1, 0, d221df78, c636dc40) >> lookuppnat+0xea(d221dec0, 0, 1, 0, d221df78, 0) >> lookupnameat+0x54() >> lookupname+0x1c(86e1990, 0, 1, 0, d221df78) >> access+0x8a() >> sys_sysenter+0x1a3() >> >> >> I can provide the dump, if anyone is interested. > >I forgot to mention, this is reproducible. It happens every time I do >a cvs checkout with netbeans 5rc1.Known bug, I think: 6360864 lofs blows chunks when file does not exist Files: update: usr/src/uts/common/fs/gfs.c update: usr/src/uts/common/fs/lofs/lofs_vnops.c Fixed in b30. Casper
On 1/15/06, Casper.Dik at sun.com <Casper.Dik at sun.com> wrote:> > >On 1/14/06, Eric Enright <eric.enright at gmail.com> wrote: > >> I seem to have bad luck.. > >> > >> Looks like an access() panic''d my system while doing a cvs checkout: > > Known bug, I think: > > 6360864 lofs blows chunks when file does not exist > > Files: > update: usr/src/uts/common/fs/gfs.c > update: usr/src/uts/common/fs/lofs/lofs_vnops.c > > > Fixed in b30.Thanks Casper. I was waiting for b31 (BrandZ patch) but I guess I''ll just see about getting their b29 patch on it. -- Eric Enright