From owner-freebsd-bugs Sat Mar 23 21:26:44 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 1C74C37B419; Sat, 23 Mar 2002 21:26:34 -0800 (PST) Received: from pool0282.cvx40-bradley.dialup.earthlink.net ([216.244.43.27] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16p0WC-0002PM-00; Sat, 23 Mar 2002 21:26:13 -0800 Message-ID: <3C9D635E.71D803B8@mindspring.com> Date: Sat, 23 Mar 2002 21:25:50 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Willie Viljoen Cc: freebsd-fs@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: Soft update instability with heavy IO and offboard IDE controller References: <20020323205001.R204-100000@phoenix.vh.laserfence.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Willie Viljoen wrote: > Although no system settings seem to exist to disable write caching from > the BIOS of my motherboard or my controller, I tried to do this with the > hw.ata.wc sysctl as described in the handbook (I know I should have > checked there fist) > > To my dismay, this sysctl claims to be read-only on my system, and I'm > still stuck with write caching enable. Could this lock be caused by the > driver for my ATA-100 controller, or do I need to add some kernel options? This parameter has to be set at boot time, either in the loader.conf file, or by hand by interrupting the load and setting it in the boot environment before continuing to boot the kernel. If you are using an IDE RAID controller, this may have to be set by talking to the controller, since the drives are not directly under your control. If it is merely a RAID controller that appears to be an ATA drive, it should propagate through, no problem, if the controller is correctly designed. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message