From owner-freebsd-current Wed Apr 5 9:49:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 532CB37B86B for ; Wed, 5 Apr 2000 09:49:20 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA78992; Wed, 5 Apr 2000 09:49:12 -0700 (PDT) (envelope-from dillon) Date: Wed, 5 Apr 2000 09:49:12 -0700 (PDT) From: Matthew Dillon Message-Id: <200004051649.JAA78992@apollo.backplane.com> To: Mathew Kanner Cc: current@FreeBSD.ORG Subject: Re: Vinum breakage References: <200004051344.JAA15337@dean.pc.sas.com> <200004051606.JAA78646@apollo.backplane.com> <20000405123724.A24249@cs.mcgill.ca> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :On Apr 05, Matthew Dillon wrote: :> (needless to say, the patch I posted is relative to FreeBSD-4.x, not 5) :> :> -Matt :> Matthew Dillon :> :> : : Here's what I got, don't put too much salt into it, somehow, :the disks are a mix of ata66 and ata33. It also happened the exact :moment I did a control-t to get the status of a tar. I'll try again :with all ata/33 or all ata/66 later tonight. : : --Mat I'm crossing my fingers and hoping it was the ^T -- wasn't there a big thread on ^T not being 'safe' a while back? I never use ^T myself. Also, as a general note to everyone, make sure you are building vinum into the kernel directly and not using it as a kld, just to ensure that it stays in sync with the kernel. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message