From owner-freebsd-hackers Thu Aug 24 10:40:00 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id KAA00416 for hackers-outgoing; Thu, 24 Aug 1995 10:40:00 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id KAA00410 for ; Thu, 24 Aug 1995 10:39:58 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA08205; Thu, 24 Aug 95 11:41:11 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9508241741.AA08205@cs.weber.edu> Subject: Re: On ESDI install. To: peter@bonkers.taronga.com (Peter da Silva) Date: Thu, 24 Aug 95 11:41:10 MDT Cc: wilko@yedi.iaf.nl, hackers@freebsd.org In-Reply-To: <199508241304.IAA19423@bonkers.taronga.com> from "Peter da Silva" at Aug 24, 95 08:04:56 am X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@freebsd.org Precedence: bulk > Since bad144 was broken for drives over 1024 cylinders, I had to > reformat a couple of times to get it down to 1 bad sector per track and > use sector sparing. That left a couple of bad sectors on wd1, took care > of them by creating a bunch of files until I had a file with the bad > block in it. Yeah, I think the relocation of the bad block replacements to the end of the partition is a bad thing. It should either go before the 'a' slice (limiting its size) or after the 'a' slice (pushing out what "might work" to get the kernel under 1024). > Xenix did all their bad blocks that way. Created a .badblock file in the > partition root and filled it with bad blocks. Was a lot more convenient than > bad144... I think the idea of "perfect media" and "file system independent block replacement" is bad. If I had my druthers, I'd probably bring back the bad block list on inode 1 instead. Consider a mounted DOS partition with bad blocks on it. What do you do when you find one under BSD? Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.