search for: ffs_alloc

...lfstab_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 761 760 759 758 757 756 755 754 753 752 751 750 749 748 747 74...

I get the above panic after nfs clients attach to this nfs server and being read/write ops on it after an unclean shutdown. I've fsck'ed the fs, and it marks it as clean, but I get this every time. It's an NFS share of a GEOM stripe (about 2TB). mode = 0100600, inum = 58456203, fs = /mnt panic: ffs_valloc: dup alloc I do have dumps from two crashes so far. This is

...7,6 +2630,10 @@ fsync(p, uap) struct file *fp; vm_object_t obj; int error; + + /* Just return if we are artificially delaying disk syncs */ + if (sync_extdelay) + return (0); if ((error = getvnode(p->p_fd, SCARG(uap, fd), &fp)) != 0) return (error); --- /usr/src/sys.org/ufs/ffs/ffs_alloc.c Fri Sep 21 21:15:21 2001 +++ ufs/ffs/ffs_alloc.c Sat Apr 12 00:06:20 2003 @@ -125,6 +125,10 @@ ffs_alloc(ip, lbn, bpref, size, cred, bn #endif /* DIAGNOSTIC */ if (size == fs->fs_bsize && fs->fs_cstotal.cs_nbfree == 0) goto nospace; + /* Speedup flushing of syncer_wokitem_pend...

...2 <Address 0x12 out of bounds>) at cpufunc.h:60 #11 0xc04bdf77 in panic (fmt=0xc0611216 "ffs_valloc: dup alloc") at /usr2/src/sys/kern/kern_shutdown.c:539 #12 0xc0577db4 in ffs_valloc (pvp=0xc0e93dd0, mode=16877, cred=0xc0d5be00, vpp=0xc52e2a50) at /usr2/src/sys/ufs/ffs/ffs_alloc.c:933 #13 0xc0591234 in ufs_mkdir (ap=0xc52e2bb8) at /usr2/src/sys/ufs/ufs/ufs_vnops.c:1333 #14 0xc05ef828 in VOP_MKDIR_APV (vop=0x12, a=0xc52e2bb8) at vnode_if.c:1251 #15 0xc051c4e5 in kern_mkdir (td=0xc0dc5a80, path=0xbfbfef56 <Address 0xbfbfef56 out of bounds>, segflg=UIO_USERSPAC...

Hi all, I was intending on trying out gjournal on a new disk i've added in my desktop. I had a look to see what the most recent patch provided by Pawel and found http://people.freebsd.org/~pjd/patches/gjournal6_20061024.patch I created the directories as per Pawel's original post (http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/001962.html) and the patch succeeded with no failed