From owner-freebsd-current Mon Mar 27 06:12:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA10532 for current-outgoing; Mon, 27 Mar 1995 06:12:17 -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 GAA10525 for ; Mon, 27 Mar 1995 06:12:05 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id AAA20934; Tue, 28 Mar 1995 00:03:13 +1000 Date: Tue, 28 Mar 1995 00:03:13 +1000 From: Bruce Evans Message-Id: <199503271403.AAA20934@godzilla.zeta.org.au> To: bde@zeta.org.au, jc@irbs.com Subject: Re: Slice errors Cc: freebsd-current@freefall.cdrom.com Sender: current-owner@FreeBSD.org Precedence: bulk >> This advice no longer applies. The bogus partition table is specially >> handled to make it work. Changing it risks introducing bugs and >> changes will be blown away by new boot blocks. >Maybe that is why I only write new boot blocks when it absolutely >necessary. The label was found and I was able to use the drive. >I just wanted to get rid of the "raw partition size != slice size" >message. I had to either increase the size of the c partition, >which disklabel would not do for some reaseon, or reduce the slice >size. The current version of disklabel can handle it (you must initialize su# in disktab and/or secperunit in `disklabel -e'). You can safely increase the size of the c partition to the size of the disk without changing the size of the partitions with file systems (keep them ending on cylinder boundaries). >Is there a reason that writing boot blocks can't re-write whatever >partition table exixts? disklabel(8) doesn't know that the partition table exists. It did in 1.1.5. That was wrong. Bruce