Date: Mon, 28 Aug 2000 22:04:34 -0400 (EDT) From: bv@wjv.com To: freebsd-isp@freebsd.org Subject: Re: untar compromises file system Message-ID: <200008290204.WAA74917@mail.wanlogistics.net> In-Reply-To: <200008282158.PAA25727@mail.fpsn.net> from Simon at "Aug 28, 2000 06:00:15 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Reply to: bv@wjv.com X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit I saw the messages about timeout - and though - hey - that's exactly the same problem I have. First off - Jim Weeks said this. ============================================== I hope someone has had a similar experience and can shed some light on this problem. While in the process of untaring an archive of the server tree I received this kernel message. Aug 28 15:46:32 host /kernel: (da1:bt0:0:1:0): Invalidating pack Aug 28 15:46:37 host last message repeated 4 times Aug 28 15:47:12 host /kernel: (da1:bt0:0:1:0): CCB 0xc8657ec0 - timed out Aug 28 15:47:29 host /kernel: bt0: btdone - Attempt to free non-active BCCB 0xc86573c0 Aug 28 15:47:29 host /kernel: (da1:bt0:0:1:0): CCB 0xc8657ec0 - timed out Aug 28 15:47:29 aurora /kernel: bt0: No longer in timeout After this happened the drive /dev/da1s1e did not seem to be configured any longer, however it still showed up under #df as being mounted as /bak. When I tried to #ls /bak nothing was there. When I tried to #umount /bak I got a device busy. I couldn't fsck, mount, or umount. I tried several other things and nothing seemed to work. I finally commented the dev out of fstab and rebooted. I was then able to run fsck on /dev/da1s1e and remount. I still need to extract the archive, but would like some feedback before trying. This is a Seagate Barracuda connected to Mylex BT958. ============================================== Then Simon added this. ============================================== I've had the same problem with Barracuda too (9/18 gigers). I wasn't using Mylex controller, though; so this could be not it. Anyhow, show us the probing for this drive from dmsg. If the firmware is 0005, then you need to upgrade it to 0010. That hopefully will fix the problem. It did for me. Thanks goes to Mike Smith for pointing it out to me. before upgrade: da0: <SEAGATE ST39236LW 0005> Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) after upgrade: da0: <SEAGATE ST39236LW 0010> Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) ============================================== > >I hope someone has had a similar experience and can shed some light on this > >problem. > > > >While in the process of untaring an archive of the server tree I received > >this kernel message. > > > >Aug 28 15:46:32 host /kernel: (da1:bt0:0:1:0): Invalidating pack > >Aug 28 15:46:37 host last message repeated 4 times > >Aug 28 15:47:12 host /kernel: (da1:bt0:0:1:0): CCB 0xc8657ec0 - timed > >out > >Aug 28 15:47:29 host /kernel: bt0: btdone - Attempt to free non-active > >BCCB 0xc86573c0 > >Aug 28 15:47:29 host /kernel: (da1:bt0:0:1:0): CCB 0xc8657ec0 - timed > >out From my dmesg - run directly from this email bt0: btdone - Attempt to free non-active BCCB 0xc32cc3c0 (da0:bt0:0:1:0): CCB 0xc32cd3c0 - timed out bt0: No longer in timeout (da0:bt0:0:1:0): CCB 0xc32cdb80 - timed out bt0: btdone - Attempt to free non-active BCCB 0xc32cc3c0 (da0:bt0:0:1:0): CCB 0xc32cdb80 - timed out bt0: No longer in timeout (da0:bt0:0:1:0): CCB 0xc32cca80 - timed out bt0: btdone - Attempt to free non-active BCCB 0xc32cc3c0 (da0:bt0:0:1:0): CCB 0xc32cca80 - timed out bt0: No longer in timeout (da0:bt0:0:1:0): CCB 0xc32cd540 - timed out bt0: btdone - Attempt to free non-active BCCB 0xc32cc3c0 (da0:bt0:0:1:0): CCB 0xc32cd540 - timed out bt0: No longer in timeout (da0:bt0:0:1:0): CCB 0xc32cd4c0 - timed out bt0: btdone - Attempt to free non-active BCCB 0xc32cc3c0 (da0:bt0:0:1:0): CCB 0xc32cd4c0 - timed out bt0: No longer in timeout (da0:bt0:0:1:0): CCB 0xc32cd3c0 - timed out ..... And about 100 more lines. This has started happening about every other day. The system freezes for a minute or so and then recovers. This same machine has had this problem in the past - and until I loaded it with 3.4 about 6 months ago - it had been running 2.2 as a mail server. These errors also occured on the 2.2. Not quit as frequent. I have noticed that these have no started happening about once or twice per week so and it's getting worse. I had three machines with the 9GB 'cudda - so I went to get the Rom rev. From the messages file on boot up. Jul 30 18:51:22 mail /kernel: ide_pci0: <Intel PIIX3 Bus-master IDE controller> rev 0x00 on pci0.7.1 Jul 30 18:51:22 mail /kernel: bt0: <Buslogic Multi-Master SCSI Host Adapter> rev 0x08 int a irq 11 on pci0.17.0 Jul 30 18:51:22 mail /kernel: bt0: BT-948 FW Rev. 5.05R Ultra Narrow SCSI Host Adapter, SCSI ID 7, 192 CCBs Jul 30 18:51:22 mail /kernel: de0: <Digital 21140A Fast Ethernet> rev 0x22 int a irq 10 on pci0.18.0 [deletia - wjv] Jul 30 18:51:23 mail /kernel: changing root device to da0s2ada0 at bt0 bus 0 target 1 lun 0 Jul 30 18:51:23 mail /kernel: da0: <IBM XP31070W !x 81K6> Fixed Direct Access SCSI-2 device Jul 30 18:51:23 mail /kernel: da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled Jul 30 18:51:23 mail /kernel: da0: 1074MB (2199878 512 byte sectors: 128H 32S/T 537C) ====================== Woops. I thought I had the Seagate in this machine. As you can see it's an IBM. The common factor among these is a BusLogic controller. This is the 498 on this machine. I've never had any problem with the BusTek/BusLogic/Mylex series - my first BL was a 542B a jillion years ago. So - could this be a driver problem in the BT. It certainly isn't a Seagate ROM problem in the the IBM. Does this help. Bill -- Bill Vermillion bv@wjv.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008290204.WAA74917>