From owner-freebsd-questions Tue Nov 10 22:49:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08845 for freebsd-questions-outgoing; Tue, 10 Nov 1998 22:49:25 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08820 for ; Tue, 10 Nov 1998 22:49:20 -0800 (PST) (envelope-from dmorrisn@u.washington.edu) Received: from u.washington.edu (D-128-95-141-86.dhcp.washington.edu [128.95.141.86]) by mailhost1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA16371 for ; Tue, 10 Nov 1998 22:49:00 -0800 Message-ID: <3649341E.DF727B80@u.washington.edu> Date: Tue, 10 Nov 1998 22:52:14 -0800 From: Don Morrison X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: questions@FreeBSD.ORG Subject: so-called "spindown" problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG During heavy disk activity, such as performing an fsck I've run into the kernel messages: wd1: interrupt timeout: wd1: status 50 error 1 wd1: wdtimeout() DMA status 4 I looked at the mail archives, and noticed some suggest that this is due to a disk spindown. My question is, how does the disk spindown during an fsck? Maybe I'm just completely ignorant here, but I can't see a logical reason for it to do this under constant disk activity. Could the messages be caused by bad disk blocks? Just looking for an alternate explanation here.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message