From owner-freebsd-current Wed Dec 18 22:30:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id WAA03628 for current-outgoing; Wed, 18 Dec 1996 22:30:24 -0800 (PST) Received: from dfw-ix1.ix.netcom.com (dfw-ix1.ix.netcom.com [206.214.98.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id WAA03619 for ; Wed, 18 Dec 1996 22:30:15 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (ala-ca13-06.ix.netcom.com [204.32.168.38]) by dfw-ix1.ix.netcom.com (8.6.13/8.6.12) with ESMTP id WAA10437 for ; Wed, 18 Dec 1996 22:29:31 -0800 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.4/8.6.9) id WAA04001; Wed, 18 Dec 1996 22:29:29 -0800 (PST) Date: Wed, 18 Dec 1996 22:29:29 -0800 (PST) Message-Id: <199612190629.WAA04001@silvia.HIP.Berkeley.EDU> To: current@freebsd.org Subject: thrashed dirs From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yesterday, I had two SCSI-related failures: == Dec 18 03:10:37 silvia /kernel: sd0(ahc0:0:0): MEDIUM ERROR info:1fb34f asc:3,0 Peripheral device write fault Dec 18 03:10:37 silvia /kernel: , retries:4 === in the middle of the night, with not much load on the machine (other than me typing or reading mail), and === Dec 18 08:34:56 silvia /kernel: sd0(ahc0:0:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Dec 18 08:35:11 silvia /kernel: SEQADDR == 0x7 Dec 18 08:35:11 silvia /kernel: Ordered Tag queued Dec 18 08:35:11 silvia /kernel: Ordered Tag sent Dec 18 08:35:11 silvia /kernel: sd0(ahc0:0:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Dec 18 08:35:11 silvia /kernel: SEQADDR == 0xf Dec 18 08:35:11 silvia /kernel: sd0(ahc0:0:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Dec 18 08:35:11 silvia /kernel: SEQADDR == 0xb Dec 18 08:35:11 silvia /kernel: ahc0: Issued Channel A Bus Reset. 3 SCBs aborted Dec 18 08:35:11 silvia /kernel: sd0(ahc0:0:0): UNIT ATTENTION asc:29,0 Dec 18 08:35:11 silvia /kernel: sd0(ahc0:0:0): Power on, reset, or bus device reset occurred Dec 18 08:35:11 silvia /kernel: , retries:3 Dec 18 08:35:11 silvia /kernel: sd1(ahc0:8:0): UNIT ATTENTION asc:29,2 Dec 18 08:35:11 silvia /kernel: , retries:4 Dec 18 08:35:11 silvia /kernel: sd1(ahc0:8:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted Dec 18 08:35:11 silvia /kernel: , retries:4 Dec 18 08:35:19 silvia /kernel: sd1(ahc0:8:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Dec 18 08:35:19 silvia /kernel: SEQADDR == 0xc Dec 18 08:35:21 silvia /kernel: sd1(ahc0:8:0): timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Dec 18 08:35:22 silvia /kernel: SEQADDR == 0xb Dec 18 08:35:22 silvia /kernel: ahc0: Issued Channel A Bus Reset. 2 SCBs aborted Dec 18 08:35:22 silvia /kernel: sd0(ahc0:0:0): UNIT ATTENTION asc:29,0 Dec 18 08:35:22 silvia /kernel: sd0(ahc0:0:0): Power on, reset, or bus device reset occurred Dec 18 08:35:22 silvia /kernel: , retries:3 Dec 18 08:35:22 silvia /kernel: sd1(ahc0:8:0): UNIT ATTENTION asc:29,2 Dec 18 08:35:22 silvia /kernel: , retries:3 === followed by a whole lot of error messages, such as === Dec 18 08:36:35 silvia /kernel: sd_strategy: Negative block number: 0xd10c1e32 Dec 18 08:36:35 silvia /kernel: bad block 1753616153, ino 446144 Dec 18 08:36:35 silvia /kernel: pid 8771 (find), uid 1289717719 on /b: bad block Dec 18 08:36:35 silvia /kernel: sd_strategy: Negative block number: 0xede56988 Dec 18 08:36:35 silvia /kernel: bad block -151866172, ino 446144 Dec 18 08:36:35 silvia /kernel: pid 8771 (find), uid 1289717719 on /b: bad block Dec 18 08:36:35 silvia /kernel: sd_strategy: Negative block number: 0x9b686b14 Dec 18 08:36:35 silvia /kernel: bad block -843827830, ino 446144 Dec 18 08:36:35 silvia /kernel: pid 8771 (find), uid 1289717719 on /b: bad block Dec 18 08:36:35 silvia /kernel: bad block 2006773318, ino 446144 Dec 18 08:36:35 silvia /kernel: pid 8771 (find), uid 1289717719 on /b: bad block : Dec 18 08:43:05 silvia /kernel: pid 8851 (find), uid -426065323 on /b: bad block Dec 18 08:43:06 silvia /kernel: bad block -874381723, ino 446162 Dec 18 08:43:06 silvia /kernel: pid 8851 (find), uid -426065323 on /b: bad block Dec 18 08:43:06 silvia /kernel: bad block -1156341551, ino 446162 Dec 18 08:43:06 silvia /kernel: pid 8851 (find), uid -426065323 on /b: bad block Dec 18 08:43:06 silvia /kernel: bad block 345491637, ino 446162 Dec 18 08:43:06 silvia /kernel: pid 8851 (find), uid -426065323 on /b: bad block Dec 18 08:43:06 silvia /kernel: bad block -1239978271, ino 446162 Dec 18 08:43:06 silvia /kernel: pid 8851 (find), uid -426065323 on /b: bad block Dec 18 08:43:06 silvia /kernel: sd_strategy: Negative block number: 0x8faa640a Dec 18 08:45:57 silvia /kernel: sd_strategy: Negative block number: 0xc2dadedc === during the /etc/daily run. Whatever the cause was, seemed to have destroyed a few directories. There was a directory called "old" in my home directory, that gives a "bad file descriptor" whenever I try to do a "ls" with anything (even just "-i"). This is the relevant part of the directory in od -c format: === 0005500 020 \0 \b 007 f o o . a s c \0 013 ,AO(B 006 \0 0005520 ,A4(B \0 004 003 o l d \0 ,A1(B Z \0 \0 200 \0 \b \f 0005540 m i s s f o n t . l o g \0 ,A|(B ,A?(B ,Ao(B === and the same three lines from od -b for those of us who are more hip in octal: === 0005500 020 000 010 007 146 157 157 056 141 163 143 000 013 317 006 000 0005520 264 000 004 003 157 154 144 000 261 132 000 000 200 000 010 014 0005540 155 151 163 163 146 157 156 164 056 154 157 147 000 374 277 357 === There was another directory (one of my mail dir's) that was so completely thrashed that I can't even start quoting the bad parts here, and some source directories. I'll uuencode and upload them to somewhere if anyone is interested. These were all on an Adaptec 2940UW / Micropolis 3243W (sd0) combination. The machine also has a Quantum XP35300W (sd1: holds system dirs and stuff) and that disk doesn't seem to have suffered any damage. Satoshi