From owner-freebsd-current@FreeBSD.ORG  Wed Apr 23 22:47:09 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4B2C637B401
	for <freebsd-current@FreeBSD.ORG>;
	Wed, 23 Apr 2003 22:47:09 -0700 (PDT)
Received: from spider.deepcore.dk
	(cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8864943FE3
	for <freebsd-current@FreeBSD.ORG>;
	Wed, 23 Apr 2003 22:47:07 -0700 (PDT)
	(envelope-from sos@spider.deepcore.dk)
Received: (from sos@localhost)
	by spider.deepcore.dk (8.12.8p1/8.12.8) id h3O5l6Vm002937;
	Thu, 24 Apr 2003 07:47:06 +0200 (CEST)
	(envelope-from sos)
From: Soeren Schmidt <sos@spider.deepcore.dk>
Message-Id: <200304240547.h3O5l6Vm002937@spider.deepcore.dk>
In-Reply-To: <200304240156.25990.michaelnottebrock@gmx.net>
To: Michael Nottebrock <michaelnottebrock@gmx.net>
Date: Thu, 24 Apr 2003 07:47:05 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL98b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=ISO-8859-1
cc: freebsd-current@FreeBSD.ORG
Subject: Re: atacontrol not reflecting disabled write cache (or rogue hdd?)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2003 05:47:09 -0000

It seems Michael Nottebrock wrote:
-- Start of PGP signed section.
> I've recently changed hw.ata.wc to 0 (via loader.conf.local) on two systems 
> and on both systems atacontrol cap still says write cache supported & enabled 
> (sysctl confirms the setting being 0). One system is 5.0-RELEASE, the other 
> 4.8-RC.
> 
> Is atacontrol lying or do the drives insist on write caching?

I'd say the drives insists on it beeing on...

-Søren