Using a : Apr 2 14:53:23 valhalla kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Apr 2 14:53:23 valhalla kernel: da0: <JetFlash TS4GJFV20 0.00> Removable Direct Access SCSI-2 device Apr 2 14:53:23 valhalla kernel: da0: 1.000MB/s transfers Apr 2 14:53:23 valhalla kernel: da0: 3936MB (8060928 512 byte sectors: 255H 63S/T 501C) Have had alot of issues trying to get it to format and be usable on this Soekris 4801. If I partition and then newfs, I get the "cg 0: bad magic number". I eventually brought up another 7.0 system on a brand new hard drive, went back into sysinstall to partition and newfs and it was fine. I did some tests over there to make directories, copy files, all was fine. I brought it back to this system, mounted /dev/da0s1d under /data2, and ran "squid -z". I then got : 2008/04/02 14:54:57| Creating Swap Directories mode = 01, inum = 23648, fs = /data2 panic: ffs_valloc: dup alloc cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper(c0afe01c,ccd0e91c,c075fd1f,c0b1f0c1,0,...) at db_trace_sel f_wrapper+0x26 kdb_backtrace(c0b1f0c1,0,c0b11ea9,ccd0e928,0,...) at kdb_backtrace+0x29 panic(c0b11ea9,1,5c60,c22fe0d4,2,...) at panic+0x10f ffs_valloc(c2308cc0,41e8,c22e9100,ccd0eb4c,c22762ec,...) at ffs_valloc+0x63a ufs_mkdir(ccd0eb90,ccd0eb74,ccd0eb90,ccd0eba4,ccd0ec68,...) at ufs_mkdir+0x95 VOP_MKDIR_APV(c0bbe660,ccd0eb90,68,ccd0eb94,0,...) at VOP_MKDIR_APV+0x42 kern_mkdir(c224c660,8245120,0,1ed,ccd0ed2c,...) at kern_mkdir+0x329 mkdir(c224c660,ccd0ecfc,8,16,ccd0ed2c,...) at mkdir+0x29 syscall(ccd0ed38) at syscall+0x335 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (136, FreeBSD ELF32, mkdir), eip = 0x2841f34b, esp = 0xbfbfeabc, ebp = 0xbfbfeb38 --- Backtrace is : bt #0 doadump () at pcpu.h:195 #1 0xc075fa57 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:417 #2 0xc075fd53 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:571 #3 0xc09494aa in ffs_valloc (pvp=0xc2308cc0, mode=16872, cred=0xc22e9100, vpp=0xccd0eb4c) at /usr/src/sys/ufs/ffs/ffs_alloc.c:968 #4 0xc0979105 in ufs_mkdir (ap=0xccd0eb90) at /usr/src/sys/ufs/ufs/ufs_vnops.c:1401 #5 0xc0a80022 in VOP_MKDIR_APV (vop=0xc0bbe660, a=0xccd0eb90) at vnode_if.c:1234 #6 0xc07e42a9 in kern_mkdir (td=0xc224c660, path=0x8245120 <Address 0x8245120 out of bounds>, segflg=UIO_USERSPACE, mode=Variable "mode" is not available. ) at vnode_if.h:654 #7 0xc07e4379 in mkdir (td=0xc224c660, uap=0xccd0ecfc) at /usr/src/sys/kern/vfs_syscalls.c:3427 #8 0xc0a6a7d5 in syscall (frame=0xccd0ed38) at /usr/src/sys/i386/i386/trap.c:1035 #9 0xc0a50620 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:196 #10 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) Fix: No ideas. :-/ How-To-Repeat: See above
BUMP....
Responsible Changed From-To: freebsd-bugs->freebsd-fs Over to maintainer(s).
I'm hitting this frequently on 9.1, freshly installed from the ISO image. I have many ffs partitions (40) and am running a simple load generation script against each mount point. The load generator just does a random collection of create, read, write, hardlink, trunc, delete from a script. There is only a single application thread running against each mount point, but there are 40 processes running against 40 different mount points. This has happened both after a hard crash + FSCK, and fairly soon after a newfs. 36 of the devices are SAS drives. 4 are SATA SSD. I'm not sure which mount point is involved, yet. Brent Welch welch@acm.org
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped