Note: your 'rename each broken file into a directory which is
	nevr used' would work fine, but wastes more disk space :)

		David/absolute

      < You can't buy love - though I've seen it rented occasionally >

On Tue, 27 Jan 1998, David Brownlee wrote:

> 	You should delete each file, use 'badsect' (check the man page),
> 	run fask, then unpack the files again.
> 
> 	If you have inode data on badsectors then it gets very painful...
> 	(I think you can newfs the disk with different parameters but
> 	just hope you do not have to go there :)
> 
> 		David/absolute
> 
> - "It was at that point I realised there might be a chance for myself
> -  as a caring human being. Unable to decide whether to feel hopeful or
> -  disgusted, I chose both and opened a bottle of wine to celebrate."
> 
> On Wed, 28 Jan 1998, Gunnar Helliesen wrote:
> 
> > As I'm unpacking the binaries on my "new" RD53 I'm seeing more of the
> > dreaded "Command 0xNN completed with result code 0xNN" messages.
> > 
> > I'm keeping track of the files affected, could a workaround be to rename
> > them, thus keeping the bad blocks allocated, and then reinstalling them?
> > 
> > Gunnar
> > 
> > --
> > Gunnar Helliesen   | Bergen IT Consult AS  | NetBSD/VAX on a uVAX II
> > Systems Consultant | Bergen, Norway        | '86 Jaguar Sovereign 4.2
> > gunnar@bitcon.no   | http://www.bitcon.no/ | '73 Mercedes 280 (240D)
> > 
> > 
> 
> 
>