Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site utah-gr.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!genrad!panda!talcott!harvard!seismo!cmcl2!philabs!pwa-b!utah-gr!thomas
From: thomas@utah-gr.UUCP (Spencer W. Thomas)
Newsgroups: net.unix
Subject: Re: Formatting Fujitsu Eagles under 4.2 BSD Unix
Message-ID: <1359@utah-gr.UUCP>
Date: Sun, 24-Feb-85 19:51:34 EST
Article-I.D.: utah-gr.1359
Posted: Sun Feb 24 19:51:34 1985
Date-Received: Fri, 1-Mar-85 20:54:58 EST
References: <232@resonex.UUCP> <478@mcvax.UUCP>
Reply-To: thomas@utah-gr.UUCP (Spencer W. Thomas)
Distribution: net
Organization: Univ of Utah CS Dept
Lines: 24
Summary: 


In article <478@mcvax.UUCP> jim@mcvax.UUCP (Jim McKie) writes:
>In article <232@resonex.UUCP> nancy@resonex.UUCP (Nancy Blachman) writes:
>    .......... I have tried formatting disks with the Unix 4.2 format 
>    routine.  It took me 13 hours on a 400 mbyte disk.  I have also 
>    formatted Eagles using the Emulex format routine which takes 2 1/2 
>    hours..............................................................
>
>But we don't do 'severe burn in', just 'worst-case media-test'. 

I think the 'severe burn in' is well worth while.  It finds many more
potentially bad spots than the other tests.  Given that any disk (Eagles
included -- from personal experience) will eventually "develop" new bad
spots, a little extra time up front is worth a lot of agony later on.
Also, adding new bad blocks to the list is a real pain -- the list of
bad blocks is kept in sorted order, so when you add a block to it, all
the ones after it must be shifted down one (i.e., you need to copy the
contents of the forwarded block to the next physical block on the disk).

-- 
=Spencer
	({ihnp4,decvax}!utah-cs!thomas, thomas@utah-cs.ARPA)
	"A sharp tongue is the only edge tool that grows keener with
	 constant use" - Washington Irving