From owner-freebsd-fs@freebsd.org Fri Mar 9 14:33:03 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BAFBCF2D14A for ; Fri, 9 Mar 2018 14:33:03 +0000 (UTC) (envelope-from martin@lispworks.com) Received: from lwfs1-cam.cam.lispworks.com (mail.lispworks.com [46.17.166.21]) by mx1.freebsd.org (Postfix) with ESMTP id D117179750; Fri, 9 Mar 2018 14:33:02 +0000 (UTC) (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (higson.cam.lispworks.com [192.168.1.7]) by lwfs1-cam.cam.lispworks.com (8.15.2/8.15.2) with ESMTP id w29EWqCg029706; Fri, 9 Mar 2018 14:32:52 GMT (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (localhost.localdomain [127.0.0.1]) by higson.cam.lispworks.com (8.14.4) id w29EWp8d015595; Fri, 9 Mar 2018 14:32:51 GMT Received: (from martin@localhost) by higson.cam.lispworks.com (8.14.4/8.14.4/Submit) id w29EWpnH015591; Fri, 9 Mar 2018 14:32:51 GMT Date: Fri, 9 Mar 2018 14:32:51 GMT Message-Id: <201803091432.w29EWpnH015591@higson.cam.lispworks.com> From: Martin Simmons To: Mars G Miro CC: trasz@freebsd.org, imp@bsdimp.com, freebsd-fs@freebsd.org In-reply-to: (message from Mars G Miro on Fri, 9 Mar 2018 15:03:06 +0800) Subject: Re: growfs only works on GPT partitioning schemes? References: <201802261411.w1QEBRt1002026@higson.cam.lispworks.com> <5A9A4B1E.8070206@anarchy.in.the.ph> <20180303113306.GB2029@brick> <201803081426.w28EQNE6003598@higson.cam.lispworks.com> X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 14:33:03 -0000 >>>>> On Fri, 9 Mar 2018 15:03:06 +0800, Mars G Miro said: > > It does have 2 snapshots in fact, this is a known problem ? > > ... > > vboxmanage showhdinfo FreeBSD11.1x64_1.vdi > > UUID: 1e5e1cab-2281-445c-9ded-10e7877cc4a4 > Parent UUID: base > State: locked read > Type: normal (base) > Location: C:\XXXXXXXXXXX\FreeBSD11.1x64_1.vdi > Storage format: VDI > Format variant: dynamic default > Capacity: 81920 MBytes > Size on disk: 28419 MBytes > Encryption: disabled > In use by VMs: FreeBSD11.1x64#1 (UUID: > 2231222c-b7aa-4976-ba5e-a4524a7d7287) [Snapshot#1 (UUID: > 54b79fb2-faa3-4072-a651-2f270022b950)] > Child UUIDs: 46e7ebef-dd79-4147-b82d-f4abf75e50d2 > > > vboxmanage showhdinfo FreeBSD11.1x64_2.vdi > > UUID: ef5bd266-fc22-402b-9ee6-126cb4d2bdaf > Parent UUID: base > State: locked write > Type: normal (base) > Location: C:\XXXXXXXXXXXXXXXXXX\FreeBSD11.1x64_2.vdi > Storage format: VDI > Format variant: dynamic default > Capacity: 61440 MBytes > Size on disk: 12084 MBytes > Encryption: disabled > In use by VMs: FreeBSD11.1x64#1 (UUID: > 2231222c-b7aa-4976-ba5e-a4524a7d7287) Yes, that is the problem (your first disk has snapshots, but you probably only resized the base vdi). Some people on the internet report success after resizing all the snapshots as well (see the "Child UUIDs" in the output and recurse). I would make a backup before doing this. Your second disk doesn't have snapshots, which is why resizing it worked. __Martin