From owner-freebsd-questions Sat May 9 15:00:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05586 for freebsd-questions-outgoing; Sat, 9 May 1998 15:00:26 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from castor.loco.net (lucy.bedford.net [206.99.145.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05552 for ; Sat, 9 May 1998 15:00:09 -0700 (PDT) (envelope-from listread@bedford.net) Received: (from listread@localhost) by castor.loco.net (8.8.8/8.8.8) id RAA10299; Sat, 9 May 1998 17:31:43 -0400 (EDT) (envelope-from listread) Message-Id: <199805092131.RAA10299@castor.loco.net> Subject: Re: Masking out bad blocks In-Reply-To: from Doug White at "May 8, 98 02:00:45 pm" To: dwhite@resnet.uoregon.edu Date: Sat, 9 May 1998 17:31:43 -0400 (EDT) Cc: freebsd-questions@FreeBSD.ORG Reply-to: djv@bedford.net From: CyberPeasant X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White wrote: > On Thu, 7 May 1998, Clod Baldrick wrote: > > > fsck tells us we have bad blocks on a file system, but apparently makes no > > attempt to mask out these blocks. Does anyone know how we can do this? > > It used to be the case that doing a low-level format would give us a table > > of bad blocks for mkfs to ignore, but scsiformat doesn't seem to do this > > -- and it completes in around a second. > > The disk should silently map these bad blocks itself. Make sure that auto > relocation is enabled by running > > scsi -f /dev/rsdX -m 1 > > and verify that AWRE and ARRE are set to 1: > > gdi,ttyp2,~/src/usr.sbin/sendmail/cf/cf,42>sudo scsi -f /dev/rsd0 -m 1 > AWRE (Auto Write Reallocation Enbld): 1 > ARRE (Auto Read Reallocation Enbld): 1 > > X = unit # of SCSI disk in question. > Have done this, and see: [root@castor /root]# scsi -f /dev/rsd0 -m 1 AWRE (Auto Write Reallocation Enbld): 0 ARRE (Auto Read Reallocation Enbld): 0 TB (Transfer Block): 0 RC (Read Continuous): 0 EER (Enable Early Recovery): 0 PER (Post Error): 0 DTE (Disable Transfer on Error): 0 DCR (Disable Correction): 0 Read Retry Count: 30 Correction Span: 0 Head Offset Count: 0 Data Strobe Offset Count: 0 Write Retry Count: 30 Recovery Time Limit: 0 [root@castor /root]# To enable reallocation, I assume I should do: scsi -f /dev/rsd0 -m 1 -e -P 3 to edit this table and save it somewhere. Right? If so, where is this saved, and what is its lifetime? From boot to boot, from power cycle to power cycle? Forever? Does it write something to the SCSI Bios' prom? Are there other settings in this (or other pages) that have odd defaults that I should, as a matter of routine, inspect? TIA, Dave -- <----. mail-to: djv@bedford.net <----|=================================== <----' Zber Qnrzbaf, Srjre Qrivyf! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message