From owner-freebsd-geom@FreeBSD.ORG Sun Jun 23 19:11:30 2013 Return-Path: Delivered-To: freebsd-geom@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 599C5271; Sun, 23 Jun 2013 19:11:30 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 33CA119A6; Sun, 23 Jun 2013 19:11:30 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5NJBUbY045769; Sun, 23 Jun 2013 19:11:30 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5NJBUVx045768; Sun, 23 Jun 2013 19:11:30 GMT (envelope-from linimon) Date: Sun, 23 Jun 2013 19:11:30 GMT Message-Id: <201306231911.r5NJBUVx045768@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-geom@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/179889: [geli] geli stopped work after updating RELEASE 9.* sources through svn [regression] X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jun 2013 19:11:30 -0000 Old Synopsis: geli stopped work after updating RELEASE 9.* sources through svn New Synopsis: [geli] geli stopped work after updating RELEASE 9.* sources through svn [regression] Responsible-Changed-From-To: freebsd-bugs->freebsd-geom Responsible-Changed-By: linimon Responsible-Changed-When: Sun Jun 23 19:11:07 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=179889 From owner-freebsd-geom@FreeBSD.ORG Sun Jun 23 23:50:02 2013 Return-Path: Delivered-To: freebsd-geom@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1D777585 for ; Sun, 23 Jun 2013 23:50:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id EA83D1284 for ; Sun, 23 Jun 2013 23:50:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5NNo19M052790 for ; Sun, 23 Jun 2013 23:50:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5NNo1cP052782; Sun, 23 Jun 2013 23:50:01 GMT (envelope-from gnats) Date: Sun, 23 Jun 2013 23:50:01 GMT Message-Id: <201306232350.r5NNo1cP052782@freefall.freebsd.org> To: freebsd-geom@FreeBSD.org Cc: From: r4721@tormail.org Subject: Re: kern/179889: [geli] geli stopped work after updating RELEASE 9.* sources through svn [regression] X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: r4721@tormail.org List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jun 2013 23:50:02 -0000 The following reply was made to PR kern/179889; it has been noted by GNATS. From: r4721@tormail.org To: bug-followup@freebsd.org Cc: Subject: Re: kern/179889: [geli] geli stopped work after updating RELEASE 9.* sources through svn [regression] Date: Sun, 23 Jun 2013 23:24:55 -0000 unable to reproduce on amd64/r252122 with or without aesni. (using benchmarks/randomio as stress generator) From owner-freebsd-geom@FreeBSD.ORG Mon Jun 24 11:06:45 2013 Return-Path: Delivered-To: freebsd-geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A5CBDFF for ; Mon, 24 Jun 2013 11:06:45 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 969631DBF for ; Mon, 24 Jun 2013 11:06:45 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r5OB6jX7000970 for ; Mon, 24 Jun 2013 11:06:45 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r5OB6jZq000968 for freebsd-geom@FreeBSD.org; Mon, 24 Jun 2013 11:06:45 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 24 Jun 2013 11:06:45 GMT Message-Id: <201306241106.r5OB6jZq000968@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-geom@FreeBSD.org Subject: Current problem reports assigned to freebsd-geom@FreeBSD.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jun 2013 11:06:45 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/179889 geom [geli] geli stopped work after updating RELEASE 9.* so o kern/178684 geom gpart(8) cannot get my GEOM tree o kern/178359 geom [geom] [patch] geom_eli: support external metadata o kern/176744 geom [geom] [patch] BIO_FLUSH not recorded by devstats o kern/170038 geom [geom] geom_mirror always starts degraded after reboot o kern/169539 geom [geom] [patch] fix ability to run gmirror on MSI MegaR a bin/169077 geom bsdinstall(8) does not use partition labels in /etc/fs f kern/165745 geom [geom] geom_multipath page fault on removed drive o kern/165428 geom [glabel][patch] Add xfs support to glabel o kern/164254 geom [geom] gjournal not stopping on GPT partitions o kern/164252 geom [geom] gjournal overflow o kern/164143 geom [geom] Partition table not recognized after upgrade R8 a kern/163020 geom [geli] [patch] enable the Camellia-XTS on GEOM ELI o kern/162690 geom [geom] gpart label changes only take effect after a re o kern/162010 geom [geli] panic: Provider's error should be set (error=0) o kern/161979 geom [geom] glabel doesn't update after newfs, and glabel s o bin/161807 geom [patch] add option for explicitly specifying metadata o kern/161752 geom [geom] glabel(8) doesn't get gpt label change o bin/161677 geom gpart(8) Probably bug in gptboot o kern/160409 geom [geli] failed to attach provider f kern/159595 geom [geom] [panic] panic on gmirror unload in vbox [regres f kern/159414 geom [isp] isp(4)+gmultipath(8) : removing active fiber pat p kern/158398 geom [headers] [patch] includes o kern/158197 geom [geom] geom_cache with size>1000 leads to panics o kern/157879 geom [libgeom] [regression] ABI change without version bump o kern/157863 geom [geli] kbdmux prevents geli passwords from being enter o kern/157739 geom [geom] GPT labels with geom_multipath o kern/157724 geom [geom] gpart(8) 'add' command must preserve gap for sc o kern/157723 geom [geom] GEOM should not process 'c' (raw) partitions fo o kern/157108 geom [gjournal] dumpon(8) fails on gjournal providers o kern/155994 geom [geom] Long "Suspend time" when reading large files fr o bin/154570 geom [patch] gvinum(8) can't be built as part of the kernel o kern/154226 geom [geom] GEOM label does not change when you modify them o kern/150858 geom [geom] [geom_label] [patch] glabel(8) is not compatibl o kern/150626 geom [geom] [gjournal] gjournal(8) destroys label o kern/150555 geom [geom] gjournal unusable on GPT partitions o kern/150334 geom [geom] [udf] [patch] geom label does not support UDF o kern/149762 geom volume labels with rogue characters o bin/149215 geom [panic] [geom_part] gpart(8): Delete linux's slice via o kern/147667 geom [gmirror] Booting with one component of a gmirror, the o kern/145818 geom [geom] geom_stat_open showing cached information for n o kern/145042 geom [geom] System stops booting after printing message "GE o kern/143455 geom gstripe(8) in RELENG_8 (31st Jan 2010) broken o kern/142563 geom [geom] [hang] ioctl freeze in zpool o kern/141740 geom [geom] gjournal(8): g_journal_destroy concurrent error o kern/140352 geom [geom] gjournal + glabel not working o kern/135898 geom [geom] Severe filesystem corruption - large files or l o kern/134113 geom [geli] Problem setting secondary GELI key o kern/133931 geom [geli] [request] intentionally wrong password to destr o bin/132845 geom [geom] [patch] ggated(8) does not close files opened a o bin/131415 geom [geli] keystrokes are unregulary sent to Geli when typ o kern/131353 geom [geom] gjournal(8) kernel lock o kern/129674 geom [geom] gjournal root did not mount on boot o kern/129645 geom gjournal(8): GEOM_JOURNAL causes system to fail to boo o kern/129245 geom [geom] gcache is more suitable for suffix based provid o kern/127420 geom [geom] [gjournal] [panic] Journal overflow on gmirrore o kern/124973 geom [gjournal] [patch] boot order affects geom_journal con o kern/124969 geom gvinum(8): gvinum raid5 plex does not detect missing s o kern/123962 geom [panic] [gjournal] gjournal (455Gb data, 8Gb journal), o kern/123122 geom [geom] GEOM / gjournal kernel lock o kern/122738 geom [geom] gmirror list "losts consumers" after gmirror de o kern/122067 geom [geom] [panic] Geom crashed during boot o kern/121364 geom [gmirror] Removing all providers create a "zombie" mir o kern/120091 geom [geom] [geli] [gjournal] geli does not prompt for pass o kern/115856 geom [geli] ZFS thought it was degraded when it should have o kern/115547 geom [geom] [patch] [request] let GEOM Eli get password fro o kern/113837 geom [geom] unable to access 1024 sector size storage o kern/113419 geom [geom] geom fox multipathing not failing back o kern/107707 geom [geom] [patch] [request] add new class geom_xbox360 to o kern/94632 geom [geom] Kernel output resets input while GELI asks for o kern/90582 geom [geom] [panic] Restore cause panic string (ffs_blkfree o bin/90093 geom fdisk(8) incapable of altering in-core geometry o kern/87544 geom [gbde] mmaping large files on a gbde filesystem deadlo o bin/86388 geom [geom] [geom_part] periodic(8) daily should backup gpa o kern/84556 geom [geom] [panic] GBDE-encrypted swap causes panic at shu o kern/79251 geom [2TB] newfs fails on 2.6TB gbde device o kern/79035 geom [vinum] gvinum unable to create a striped set of mirro o bin/78131 geom gbde(8) "destroy" not working. 78 problems total. From owner-freebsd-geom@FreeBSD.ORG Wed Jun 26 07:31:37 2013 Return-Path: Delivered-To: geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 84F59F28 for ; Wed, 26 Jun 2013 07:31:37 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (gw.catspoiler.org [75.1.14.242]) by mx1.freebsd.org (Postfix) with ESMTP id 686DA12F0 for ; Wed, 26 Jun 2013 07:31:34 +0000 (UTC) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id r5Q7VMBY002283 for ; Wed, 26 Jun 2013 00:31:26 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201306260731.r5Q7VMBY002283@gw.catspoiler.org> Date: Wed, 26 Jun 2013 00:31:22 -0700 (PDT) From: Don Lewis Subject: funkiness when resizing a BSD slice To: geom@FreeBSD.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jun 2013 07:31:37 -0000 I've got a machine that used to dual boot FreeBSD and a Fedora. It had one disk slice for FreeBSD, another slice for Fedora, and a third slice that was marked as Linux swap that both FreeBSD and Linux used as swap. The FreeBSD slice had only an "a" ufs partition that covered the entire slice (in addition to the "c" partition). FreeBSD outgrew its available space. Since I wasn't using the Fedora slice anymore, I wanted to delete the Fedora slice, grow the FreeBSD slice, grow the "a" partition, and the run growfs to expand the ufs filesystem. Things started off smoothly, but I ran into problems after I grew the FreeBSD slice. I eventually stumbled around until I expanded the "a" partition, but then bsdlabel whined about the size of the "c" partition until I manually edited its size, contrary to the instructions. The system is running a fairly recent version of 10-CURRENT, but I don't think this matters much. The following script will reproduce the problem: #!/bin/sh -x provider=`mdconfig -a -t swap -s 100m` unit=`echo $provider | sed -e 's/md//'` gpart create -s mbr $provider gpart add -t freebsd -s 50m -i 1 $provider gpart create -s bsd ${provider}s1 gpart add -t freebsd-ufs -i 1 ${provider}s1 gpart show $provider gpart show ${provider}s1 bsdlabel ${provider}s1 gpart resize -i 1 $provider gpart show $provider gpart show ${provider}s1 bsdlabel ${provider}s1 gpart resize -i 3 ${provider}s1 gpart resize -i 1 ${provider}s1 gpart show ${provider}s1 bsdlabel ${provider}s1 echo q | env EDITOR=/bin/ed bsdlabel -e /dev/${provider}s1 gpart show ${provider}s1 bsdlabel ${provider}s1 gpart resize -i 1 ${provider}s1 gpart show ${provider}s1 bsdlabel ${provider}s1 mdconfig -d -u $unit If I run it, I get the following output: + mdconfig -a -t swap -s 100m + provider=md0 + echo md0 + sed -e s/md// + unit=0 + gpart create -s mbr md0 md0 created + gpart add -t freebsd -s 50m -i 1 md0 md0s1 added + gpart create -s bsd md0s1 md0s1 created + gpart add -t freebsd-ufs -i 1 md0s1 md0s1a added + gpart show md0 => 9 204791 md0 MBR (100M) 9 102393 1 freebsd (50M) 102402 102398 - free - (50M) + gpart show md0s1 => 0 102393 md0s1 BSD (50M) 0 102393 1 freebsd-ufs (50M) + bsdlabel md0s1 # /dev/md0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 102393 0 4.2BSD 0 0 0 c: 102393 0 unused 0 0 # "raw" part, don't edit Everything looks fine so far ... + gpart resize -i 1 md0 md0s1 resized + gpart show md0 => 9 204791 md0 MBR (100M) 9 204786 1 freebsd (100M) 204795 5 - free - (2.5k) This looks fine, too ... + gpart show md0s1 => 0 102393 md0s1 BSD (100M) 0 102393 1 freebsd-ufs (50M) Hmn ... the mediasize of md0s1 has changed, but not its last sector number. + bsdlabel md0s1 # /dev/md0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 102393 0 4.2BSD 0 0 0 c: 102393 0 unused 0 0 # "raw" part, don't edit Bsdlabel doesn't see anything change ... + gpart resize -i 3 md0s1 gpart: invalid partition index It won't let me resize the "c" partition because the gpe_internal flag is set on it. + gpart resize -i 1 md0s1 md0s1a resized ... it lies ... + gpart show md0s1 => 0 102393 md0s1 BSD (100M) 0 102393 1 freebsd-ufs (50M) + bsdlabel md0s1 # /dev/md0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 102393 0 4.2BSD 0 0 0 c: 102393 0 unused 0 0 # "raw" part, don't edit ... no change in the size of the "a" partition. + echo q + env EDITOR=/bin/ed bsdlabel -e /dev/md0s1 228 bsdlabel: partition c doesn't cover the whole unit! bsdlabel: An incorrect partition c may cause problems for standard system utilities + gpart show md0s1 => 0 204786 md0s1 BSD (100M) 0 102393 1 freebsd-ufs (50M) 102393 102393 - free - (50M) Now the last sector number of md0s1 has been updated (because a retaste was triggered?), but ... + bsdlabel md0s1 # /dev/md0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 102393 0 4.2BSD 0 0 0 c: 102393 0 unused 0 0 # "raw" part, don't edit bsdlabel: partition c doesn't cover the whole unit! bsdlabel: An incorrect partition c may cause problems for standard system utilities ... the size of the "c" partition hasn't and bsdlabel is unhappy. + gpart resize -i 1 md0s1 md0s1a resized + gpart show md0s1 => 0 204786 md0s1 BSD (100M) 0 204786 1 freebsd-ufs (100M) + bsdlabel md0s1 # /dev/md0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 204786 0 4.2BSD 0 0 0 c: 102393 0 unused 0 0 # "raw" part, don't edit bsdlabel: partition c doesn't cover the whole unit! bsdlabel: An incorrect partition c may cause problems for standard system utilities ... but I finally managed to grow the "a" partition. The "c" partition is still messed up and the only way to fix it is to ignore the instructions that say not to edit it. + mdconfig -d -u 0 I poked around inside the twistly little passages inside geom and I *think* the proper way to fix this is to add a resize method to g_bsd_class in geom_bsd.c. I *think* this resize method should update d_secperunit in the disklabel at the start of the bsd slice, update gpt_last in the basetable, and update p_size in the "c" partition entry. From owner-freebsd-geom@FreeBSD.ORG Sat Jun 29 22:16:30 2013 Return-Path: Delivered-To: geom@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0AC21ADA; Sat, 29 Jun 2013 22:16:30 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward19.mail.yandex.net (forward19.mail.yandex.net [IPv6:2a02:6b8:0:1402::4]) by mx1.freebsd.org (Postfix) with ESMTP id B1D8D1828; Sat, 29 Jun 2013 22:16:29 +0000 (UTC) Received: from smtp16.mail.yandex.net (smtp16.mail.yandex.net [95.108.252.16]) by forward19.mail.yandex.net (Yandex) with ESMTP id 95FD91121562; Sun, 30 Jun 2013 02:16:26 +0400 (MSK) Received: from smtp16.mail.yandex.net (localhost [127.0.0.1]) by smtp16.mail.yandex.net (Yandex) with ESMTP id 615BE6A06AD; Sun, 30 Jun 2013 02:16:26 +0400 (MSK) Received: from v10-166-195.yandex.net (v10-166-195.yandex.net [84.201.166.195]) by smtp16.mail.yandex.net (nwsmtp/Yandex) with ESMTP id Jm9CZ0wHn9-GPBOHLDU; Sun, 30 Jun 2013 02:16:25 +0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1372544186; bh=txQ9kYXpB6N0qf6eWCT4hzbrZAzTrN6xE7aIWWKwAU0=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:X-Enigmail-Version:Content-Type: Content-Transfer-Encoding; b=k3vt41PaGPxJ+352fGVW+OyyMG3XVyRT+XUi57quzzc6sloiRUUoPtFtLbyhWiOHm NqW+xcAXpDRjURtMOsLuStrM18IR+Du1LfpgkOduqAzFsk48pXPCBQ+OrTyNsk5oq5 PKKlYmMMf2bt+F74npaFJpVMZ575Hiv1tDpgXleA= Authentication-Results: smtp16.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <51CF5C09.2090303@yandex.ru> Date: Sun, 30 Jun 2013 02:13:29 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Don Lewis Subject: Re: funkiness when resizing a BSD slice References: <201306260731.r5Q7VMBY002283@gw.catspoiler.org> In-Reply-To: <201306260731.r5Q7VMBY002283@gw.catspoiler.org> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: geom@FreeBSD.org X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jun 2013 22:16:30 -0000 On 26.06.2013 11:31, Don Lewis wrote: > I've got a machine that used to dual boot FreeBSD and a Fedora. It had > one disk slice for FreeBSD, another slice for Fedora, and a third slice > that was marked as Linux swap that both FreeBSD and Linux used as swap. > The FreeBSD slice had only an "a" ufs partition that covered the entire > slice (in addition to the "c" partition). > > FreeBSD outgrew its available space. Since I wasn't using the Fedora > slice anymore, I wanted to delete the Fedora slice, grow the FreeBSD > slice, grow the "a" partition, and the run growfs to expand the ufs > filesystem. Things started off smoothly, but I ran into problems after > I grew the FreeBSD slice. I eventually stumbled around until I expanded > the "a" partition, but then bsdlabel whined about the size of the "c" > partition until I manually edited its size, contrary to the > instructions. Hi, yes, the described problem exists. I see two ways how this can be solved. 1. geom resize method. It is called, when parent provider is growing. So in some way this can be handled by each specific partitioning scheme. 2. Add to the gpart(8) and gpart(4) support to call gpart resize without -i parameter (like this was done recently for set/unset attributes). Without "-i" resize command will update partition table metadata, if it contains some information about available size. > I poked around inside the twistly little passages inside geom and I > *think* the proper way to fix this is to add a resize method to > g_bsd_class in geom_bsd.c. I *think* this resize method should update > d_secperunit in the disklabel at the start of the bsd slice, update > gpt_last in the basetable, and update p_size in the "c" partition entry. geom_bsd isn't used usually, it was replaced with g_part_bsd. -- WBR, Andrey V. Elsukov