Path: utzoo!news-server.csri.toronto.edu!torsqnt!hybrid!scifi!bywater!uunet!dsuvax!ghelmer
From: ghelmer@dsuvax.uucp (Guy Helmer)
Newsgroups: comp.os.minix
Subject: Re: /etc/update is hanging
Message-ID: <1991Mar15.170118.3983@dsuvax.uucp>
Date: 15 Mar 91 17:01:18 GMT
References: <1991Mar12.225454.19910@viewlogic.com>
Organization: Dakota State University
Lines: 36

In <1991Mar12.225454.19910@viewlogic.com> greg@suntan.viewlogic.com (Gregory Larkin) writes:

>Hi all,

>I am trying to build a new libc.a.  My 30 meg partition is
>almost full, and I happen to know that there are bad blocks
>out in the far reaches of the partition.

>When I first made the partition, I ran "readall /dev/hd6" to
>find the bad blocks.  I then ran "badblocks" to get rid of 
>them (I think!).

You must have run the original 1.5 badblocks.  It removes the
wrong blocks from the free zone bitmap when the block numbers are
greater than 8191.

>Also, when I run fsck after badblocks, I get weird messages
>about duplicate zones and missing bitmaps?  Is this normal?

fsck -r /dev/hd? has always fixed badblock's mistakes for me.  If you
have files that ended up on the bad part of the disk, you should rm them
or fsck won't be able to help you out.  de(8 or 1?) can help you
find out if a file has been placed in a bad zone.  It's not normal
for fsck to complain about anything, and if it does, your file system
contains an inconsistency that should be fixed, usually by running
fsck -r.

>Thanks for any help,

>Greg Larkin

-- 
Guy Helmer                       | helmer@sdnet.bitnet
Dakota State University          | dsuvax!ghelmer@wunoc.wustl.edu
(605) 256-5264, (605) 256-2788   | uunet!dsuvax!ghelmer
Ahh, if weddings were as easy to design as software...