Date: Thu, 19 Oct 2000 11:53:25 +0100 From: dbhague@allstor-sw.co.uk To: dbhague@allstor-sw.co.uk Cc: freebsd-scsi@FreeBSD.org, freebsd-fs@FreeBSD.org, gibbs@scsiguy.com, mjacob@feral.com, Andre Albsmeier <andre.albsmeier@mchp.siemens.de>, smcintyre@allstor-sw.co.uk, paul@originative.co.uk Subject: Re: Stressed SCSI subsystem locks up the system Message-ID: <8025697D.003BD2D1.00@mail.plasmon.co.uk>
next in thread | raw e-mail | index | archive | help
Further to my earlier mails we have now trapped a failure and I enclose the
stack trace. I have typed this in but do have a picture of the screen if
required.
We have also had several more of the >panic ffs_blkfree freeing free frags type
errors.
I believe by moving to the current 4.1 stable we now have a file system problem,
Any comments would be welcome.
Regards Dave
start = 0, len =2, fs = /RAID
panic: ffs_alloccg: map corrupted
Debugger("panic")
Stopped at Debugger+0x34: movb $0,in_Debugger.396
db> tr
Debugger(c02d0063) at Debugger+0x34
panic(c02e5f7f,c02e5f60,0,2,c0b388d4) at panic+0x70
ffs_mapsearch(c0b38800,c47cc000,2bc0008,3,578) at ffs_mapsearch+0x128
ffs_alloccg((c107e400,578,2bc0008,400) at ffs_alloccg+0x21e
ffs_hashalloc(c107e400,578,2bc0008,400,c0246748) at ffs_hashalloc+0x23
ffs_alloc(c107e400,0,2bc0008,400,c0b2c000) at ffs_alloc_0x129
ffs_balloc(c871ae2c,c8cc6780,c11d0a40,c871aedc,c88b0300) at fss_balloc+0x476
ffa_write(c871ae6c,c7cf01e0,c7cf01e0,400,1) at ffs_write+0x33d
vn_write(c11d0a40,c871aedc,c0b2c000,0,c7cf01e0) at vn_write+0x160
dofilewrite(c7f01e0,c11d0a40,3,80567a0,400) at dofilewrite+0xb1
write(c7cf01e0,c871af80,0,180,bfbffbcc) at write+0x33
syscall2(bfbf002f,bfbf002f,bfbf002f,bfbffbcc,180) at syscall+0x205
Xint0x80_syscall() at Xint0x80_syscall+0x25
db>_
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8025697D.003BD2D1.00>