Mikhail A. Sokolov wrote... > Hello, > > we're experiencing repeated 4.0-C (as of today, something around 12:00 > GMT, 1999-03-16) ufs_dirbad() panics, which are the > following (below), which usually occur when squid is running. The box > doesn't have ccd, nor vinum nor anything fancy in it's config, no SMP either. > Squid's spool is hardware (IFT3102) RAID1, 2x9gb (i.e. 4 disks): > /var/crash# gdb -k kernel.1 vmcore.1 > IdlePTD 2682880 > initial pcb at 21c7b8 > panicstr: ufs_dirbad: bad dir > panic messages: > --- > panic: ufs_dirbad: bad dir
I have no idea why you're getting a panic, but I do have a question... > syncing disks... 134 63 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up > (da1:ahc1:0:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da1:ahc1:0:1:0): ILLEGAL REQUEST asc:20,0 > (da1:ahc1:0:1:0): Invalid command operation code > (da2:ahc1:0:2:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da2:ahc1:0:2:0): ILLEGAL REQUEST asc:20,0 > (da2:ahc1:0:2:0): Invalid command operation code > (da3:ahc1:0:3:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 > (da3:ahc1:0:3:0): ILLEGAL REQUEST asc:20,0 > (da3:ahc1:0:3:0): Invalid command operation code Are you *sure* you're running -current as of today? Justin put code in to silence Illegal request error messages from the sync cache command. What revision of scsi_da.c do you have, and has it been modified? Ken -- Kenneth Merry k...@plutotech.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
