search for: lockmgr

...tch () at machine/globals.h:119 #1 0x8014a1f9 in tsleep (ident=0x8a3d2200, priority=8, wmesg=0x80263d4a "inode", timo=0) at /usr/src/sys/kern/kern_synch.c:479 #2 0x80141507 in acquire (lkp=0x8a3d2200, extflags=16777280, wanted=1536) at /usr/src/sys/kern/kern_lock.c:147 #3 0x8014179c in lockmgr (lkp=0x8a3d2200, flags=16973826, interlkp=0xbdc27b6c, p=0xc26fa9c0) at /usr/src/sys/kern/kern_lock.c:355 #4 0x80172b73 in vop_stdlock (ap=0xc2a95d1c) at /usr/src/sys/kern/vfs_default.c:256 #5 0x801f0955 in ufs_vnoperate (ap=0xc2a95d1c) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2376 #6 0x8017d450 in vn...

I started sharing out zfs filesystems via NFS last week using sharenfs=on. That seems to work fine until I reboot. Turned out the NFS server wasn''t enabled - I had to enable nfs/server, nfs/lockmgr and nfs/status manually. This is a stock SXCR b49 (ZFS root) install - don''t think I''d changed anything much. Shouldn''t a ZFS share be permanently enabling NFS? -- Rasputin :: Jack of All Trades - Master of Nuns http://number9.hellooperator.net/

...ls/gdb/../../../../contrib/gdb/gdb/dbxread.c line 2627 in elfstab_build_psymtabs Deprecated bfd_read called at /usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line 933 in fill_symbuf IdlePTD at phsyical address 0x005bf000 initial pcb at physical address 0x004dbb00 panicstr: lockmgr: locking against myself panic messages: --- panic: ffs_alloccg: map corrupted syncing disks... 145 111 102 41 37 31 31 31 31 31 31 31 panic: lockmgr: locking against myself Uptime: 2d9h18m37s dumping to dev #ad/0x30031, offset 4718752 dump ata3: resetting devices .. done 767 766 765 764 763 762 7...

Hi all, I'm extremely puzzled by the behaviour of one of my Samba servers. It's been working fine for yonks, and this morning (abuout 11:32) it just stopped. (mostly) Connecting to shares still works. Navigating the tree till works. Changing (DOS) attributes still works. But actually opening files and reading the contents doesn't work. The client just times out (Win 3.11, and

...tch () at machine/globals.h:119 #1 0x8014a1f9 in tsleep (ident=0x8a4ef600, priority=8, wmesg=0x80263d4a "inode", timo=0) at /usr/src/sys/kern/kern_synch.c:479 #2 0x80141507 in acquire (lkp=0x8a4ef600, extflags=16777280, wanted=1536) at /usr/src/sys/kern/kern_lock.c:147 #3 0x8014179c in lockmgr (lkp=0x8a4ef600, flags=16973826, interlkp=0xbde68aec, p=0xbf57b000) at /usr/src/sys/kern/kern_lock.c:355 #4 0x80172b73 in vop_stdlock (ap=0xbfc2dd1c) at /usr/src/sys/kern/vfs_default.c:256 #5 0x801f0955 in ufs_vnoperate (ap=0xbfc2dd1c) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2376 #6 0x8017d450 in vn...

...t 0 c037b4a0 c040d000 0 0 0 000204 3 sched c037b4a0 swapper The hung tasks look like this: db> t 446 mi_switch(c34ab600,1000040,0,0,ffffffff) at mi_switch+0x1c8 tsleep(c34ab600,8,c031a54a,0,c34ab600) at tsleep+0x1d1 acquire(c34ab600,1000040,600,c34ab600,20002) at acquire+0xbc lockmgr(c34ab600,1030002,defc4e6c,e75e1220,defc4e00) at lockmgr+0x2cc vop_stdlock(e766bd28,e766bd38,c01fa02c,e766bd28,defc4e00) at vop_stdlock+0x42 ufs_vnoperate(e766bd28) at ufs_vnoperate+0x15 vn_lock(defc4e00,20002,e75e1220) at vn_lock+0x9c lookup(e766bed0,0,e766bed0,e766bed0,e75e1220) at lookup+0x81 nam...

Dear Sirs. It seems to me a never ending story. We run a box with a TYAN Thunder 2500 Dual SMP mainboard, 2GB ECC Tyan certified memory, AMI Enterprise 1600 RAID adapter and additional Intel 1000/Pro server type (64 bit) GBit LAN NIC. With FreeBSD 4.8 this was stable, but to achive this state was really hard! It is a story similar to that what happend when we changed towards FreeBSD