From owner-freebsd-hackers Thu May 6 14: 2: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (Postfix) with SMTP id 253C815A36 for ; Thu, 6 May 1999 14:02:04 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 15342 invoked from network); 6 May 1999 21:02:03 -0000 Received: from shell-1.enteract.com (dscheidt@207.229.143.40) by thor.enteract.com with SMTP; 6 May 1999 21:02:03 -0000 Received: from localhost (dscheidt@localhost) by shell-1.enteract.com (8.9.3/8.9.2) with SMTP id QAA47927; Thu, 6 May 1999 16:02:03 -0500 (CDT) (envelope-from dscheidt@enteract.com) X-Authentication-Warning: shell-1.enteract.com: dscheidt owned process doing -bs Date: Thu, 6 May 1999 16:02:03 -0500 (CDT) From: David Scheidt To: Zhihui Zhang 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 On Thu, 6 May 1999, Zhihui Zhang wrote: :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?). I often build machines with more than one FreeBSD slice, and only one root filesystem. : :What kind of panic? The kernel is a trusted program anyway. One that hoses the in-core copy of the superblock, and then writes it back out to disk would have this effect. Never seen this on FreeBSD, but I dealt with a bunch of NeXTstep machines that would do this on every other panic. A physical disk failure could casue this too. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message