From owner-freebsd-current Fri Aug 23 12:52:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01131 for current-outgoing; Fri, 23 Aug 1996 12:52:18 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA01123 for ; Fri, 23 Aug 1996 12:52:09 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA01307; Fri, 23 Aug 1996 21:51:28 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA04360; Fri, 23 Aug 1996 21:51:27 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id VAA01255; Fri, 23 Aug 1996 21:44:44 +0200 (MET DST) From: J Wunsch Message-Id: <199608231944.VAA01255@uriah.heep.sax.de> Subject: Re: -current kills harddrives To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Fri, 23 Aug 1996 21:44:44 +0200 (MET DST) Cc: nirva@ishiboo.com Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <20865.840816321@time.cdrom.com> from "Jordan K. Hubbard" at "Aug 23, 96 09:05:21 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > I seriously doubt that -current is killing your hard drives. > Some things you just can't do from software, even if you wanted > to. At least not this way... Basically, the drive in question seem to have initiated a SCSI bus reset. It's probably a problem in our drivers if the system doesn't survive the bus reset, but the origin of the problem is a hardware fault of your drive. Btw., i've once seen strange error messages caused by weak power supply cabling. Yes, i was finally fully convinced that the disk must be bad, bought a replacement, transfered one gig worth of data over to the replacement (which worked fine), and had all my troubles back once i had mounted the new drive in the same location as the supposedly to be broken old one. :-/ -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)