From owner-freebsd-isp Mon Aug 28 14:41: 2 2000 Delivered-To: freebsd-isp@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.prod.itd.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 1D5C537B43E for ; Mon, 28 Aug 2000 14:40:53 -0700 (PDT) Received: from veager.siteplus.net (1Cust185.tnt7.chattanooga.tn.da.uu.net [63.28.246.185]) by snipe.prod.itd.earthlink.net (8.9.3-EL_1_3/8.9.3) with ESMTP id OAA21755 for ; Mon, 28 Aug 2000 14:40:35 -0700 (PDT) Date: Mon, 28 Aug 2000 17:40:29 +0000 (GMT) From: Jim Weeks To: freebsd-isp@freebsd.org Subject: untar compromises file system Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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. Any ideas would be appreciated. -- Jim Weeks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message