From owner-freebsd-hardware Mon Oct 27 15:43:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA06379 for hardware-outgoing; Mon, 27 Oct 1997 15:43:32 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from lafcol (lafcol.lafayette.edu [139.147.8.5]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA06365 for ; Mon, 27 Oct 1997 15:43:25 -0800 (PST) (envelope-from knollm@lafcol.lafayette.edu) Received: from bishop by lafcol (SMI-8.6/SMI-SVR4) id SAA20796; Mon, 27 Oct 1997 18:42:13 -0500 Message-Id: <3.0.32.19971027183611.00982930@lafcol.lafayette.edu> X-Sender: knollm@lafcol.lafayette.edu X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 27 Oct 1997 18:42:52 -0500 To: cgull+usenet-877838850@smoke.marlboro.vt.us (john hood), hardware@freebsd.org From: Babumpabajard Subject: Re: Harddrive powerdowns Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 12:09 AM 10/26/97 -0400, you wrote: >Mike Smith writes: > > The wd driver times the operation out and retries it. AFAIR most > > operations are tried at least 3 times before giving up. > >And in -current, the driver now waits longer (10s) before the first >retry, eliminating those nattering errors. I can not figure out why my HD is spinning up so frequently. I set the time down to 1 minute, with no one logged in, only process other than defualt but sshd, and the system still reads. There's 48megs of RAM, so I can't immagine it needs to swap. Is there a way to determine what is using my harddrive? Michael