From owner-freebsd-current Sat Apr 1 06:47:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA12754 for current-outgoing; Sat, 1 Apr 1995 06:47:52 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA12748 for ; Sat, 1 Apr 1995 06:47:47 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id AAA12819; Sun, 2 Apr 1995 00:43:34 +1000 Date: Sun, 2 Apr 1995 00:43:34 +1000 From: Bruce Evans Message-Id: <199504011443.AAA12819@godzilla.zeta.org.au> To: Kai.Vorma@hut.fi Subject: Re: panic: update: rofs mod Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >sd0d: start 0, end 2117631, size 2117632 >sd0: rejecting partition in BSD label: it isn't entirely within the slice >but otherwise all seemed OK. I run 'disklabel sd0' to see that all >partitions were still there and rebooted again: ># reboot >syncing disks... done >fs = / >panic: update: rofs mod Did you get this without writing to the block device? `disklabel sd0' should use the character device (and not write to it). >Then I brought the system to multi-user and used disklabel -e to get >rid of that offending sd0d partition. Then I rebooted again to >singe-user and found out that reboot no longer causes panic. This is hard to explain. >The only strange thing now is that the slice code prints out my >partitions thrice: >sd0s1: start 32, end = 204799, size 204768: OK >sd0s2: start 204800, end = 2117631, size 1912832: OK >sd0s1: start 32, end = 204799, size 204768: OK >sd0s2: start 204800, end = 2117631, size 1912832: OK >sd0s1: start 32, end = 204799, size 204768: OK >sd0s2: start 204800, end = 2117631, size 1912832: OK >Is that normal? Yes. See old FreeBSD-current mail. Bruce