Date: Thu, 4 Oct 2001 17:43:05 +0100 From: David Taylor <davidt@yadt.co.uk> To: Jun Kuriyama <kuriyama@imgsrc.co.jp> Cc: semenu@FreeBSD.org, Current <FreeBSD-current@FreeBSD.org> Subject: Re: ntfs panic (lockmgr: not exclusive lock holder 470 unlocking) Message-ID: <20011004174305.A82268@gattaca.yadt.co.uk> In-Reply-To: <7mbsjnmt4p.wl@waterblue.imgsrc.co.jp>; from kuriyama@imgsrc.co.jp on Thu, Oct 04, 2001 at 22:28:38 %2B0900 References: <7mbsjnmt4p.wl@waterblue.imgsrc.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 04 Oct 2001, Jun Kuriyama wrote:
> I tried to use mount_ntfs, but it panic'ed.
>
>
> % sudo mount -t ntfs /dev/ad0s1 /mnt
> % cd /mnt
> % ls -la
> panic: lockmgr: pid 551, not exclusive lock holder 470 unlocking
> Debugger("panic")
> Stopped at Debugger+0x44: pushl %ebx
> db> t
> Debugger() at Debugger+0x44
> panic(c02ef100,227,c02ef0e0,1d6,cab5f740) at panic+0x70
> lockmgr(cb5f7dc,6,cab5f7ac,ca376404,caad4bf4) at lockmgr+0x369
> vop_stdunlock(caad4be4,cab5f740,ca376404,c031dbc0,cab5f740) at vop_stdunlock+0x22
> ntfs_inactive(caad4c08,cab5f740,0,c031db00,cab5f740) at ntfs_inactive+0x54
I reported the same panic a while ago. It appears to have been caused by
the last large KSE commit.
--
David Taylor
davidt@yadt.co.uk
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?20011004174305.A82268>