From owner-freebsd-stable@FreeBSD.ORG Sat Jun 9 15:27:46 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF92B1065675 for ; Sat, 9 Jun 2012 15:27:46 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2E7598FC20 for ; Sat, 9 Jun 2012 15:27:45 +0000 (UTC) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id q59FRTxN069657; Sat, 9 Jun 2012 17:27:44 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id q59FRTeg069656; Sat, 9 Jun 2012 17:27:29 +0200 (CEST) (envelope-from olli) Date: Sat, 9 Jun 2012 17:27:29 +0200 (CEST) Message-Id: <201206091527.q59FRTeg069656@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, lists@opsec.eu In-Reply-To: <20120608144621.GA74475@home.opsec.eu> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.9.6-20101126 ("Burnside") (UNIX) (FreeBSD/6.4-PRERELEASE-20080904 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.9 (lurza.secnetix.de [127.0.0.1]); Sat, 09 Jun 2012 17:27:45 +0200 (CEST) Cc: Subject: Re: Experience with Intel SATA and fbsd 8.3-amd64 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, lists@opsec.eu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2012 15:27:46 -0000 Kurt Jaeger wrote: > I have a problem with some host: If I put heavy IO load on that > system, write errors happen, and then it crashes. What kind of write errors, exactly? What messages do you get on the console? It's also worth mentioning that such problems could also be caused by bad RAM, or even by the power supply (though the latter is unlikely in this case, I think). Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs." -- Robert Firth