Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!henry
From: henry@utzoo.UUCP (Henry Spencer)
Newsgroups: net.unix-wizards
Subject: Re: inode numbers
Message-ID: <5688@utzoo.UUCP>
Date: Mon, 17-Jun-85 12:17:16 EDT
Article-I.D.: utzoo.5688
Posted: Mon Jun 17 12:17:16 1985
Date-Received: Mon, 17-Jun-85 12:17:16 EDT
References: <1725@aecom.UUCP> <44700005@gypsy.UUCP>, <358@cheviot.UUCP>
Organization: U of Toronto Zoology
Lines: 23

> On at least some European V7 systems, inode 1 is used for a list of bad
> blocks. Basically mkfs has been extended to include a secret undocumented
> option (in the true Unix tradition!) which scans the whole device and puts
> any funny blocks in inode 1 out of harms way.
> ...
> I have no idea whether this feature is standard (but undocumented), or a
> local hack, but I have seen it on more than one system.

It's sort of semi-standard.  The original V7 had hooks in mkfs for putting
a bad-block list in inode 1, but didn't bother actually doing it (the
give-me-a-bad-block-number routine was a stub that always returned "none").
Many people have noticed this and extended mkfs, in one way or another, to
actually install a bad-block list.

> As far as I know, nothing else
> pays any attention to the list - it is just a device for keeping blocks off
> the free list without upsetting fsck.

Actually, several other programs (e.g. dump and restor) needed slight fixes
to make them keep their hands off inode 1, but these were pretty trivial.
-- 
				Henry Spencer @ U of Toronto Zoology
				{allegra,ihnp4,linus,decvax}!utzoo!henry