From owner-freebsd-hackers Thu May 6 13:36:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sol (cs1-gw.cs.binghamton.edu [128.226.171.72]) by hub.freebsd.org (Postfix) with SMTP id AD96B14C45 for ; Thu, 6 May 1999 13:35:45 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from localhost (zzhang@localhost) by sol (SMI-8.6/8.6.9) with SMTP id QAA15684; Thu, 6 May 1999 16:25:02 -0400 Date: Thu, 6 May 1999 16:25:01 -0400 (EDT) From: Zhihui Zhang To: David Scheidt Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Copies of superblocks in FFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for your reply, but I still have a little problem with it: > :Also, except for the root filesystem (/), all other filesystems (/var, > :/usr, etc.) do not have the (boot code + disklabel) installed, these space > :are also wasted (8192 bytes for each non-root filesystem). > > It is very handy to be able to make a filesytem bootable after it has been > created. Much easier than dumping the filesytem, remaking the filesytem, and > then restoring it. I'll pay 16K per filesystem for this. But the BIOS always read boot blocks from the beginning of a FreeBSD slice, which is the root filesystem space (or can we let other non-root filesystems to occupy the beginning of the FreeBSD slice?). > :BTW, the hard disks are more stable nowadays and any bad sectors may have > :been hidden by the disk controllers (the filesystem does not have to deal > :with them). > > Panics still can leave the primary superblock hosed. Trust me. What kind of panic? The kernel is a trusted program anyway. Thanks for you help. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message