From owner-freebsd-fs@freebsd.org Thu Mar 8 13:54:04 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 BC1A6F3383F for ; Thu, 8 Mar 2018 13:54:04 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-ua0-x230.google.com (mail-ua0-x230.google.com [IPv6:2607:f8b0:400c:c08::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 183397B84C for ; Thu, 8 Mar 2018 13:54:04 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-ua0-x230.google.com with SMTP id f6so3965949ual.0 for ; Thu, 08 Mar 2018 05:54:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=A4IlQeuqiYsDQ4SAUvSOxD4U847D4YvgodIGA6E77gc=; b=smrDQu7q4JkTiTK54v4KdayvKzMgcaLx0lbL4YfGYlY1KkgBF4WJfAFIENAuyN4CzQ qofKxkRddRdp9r3wGCDLwmUuFfCRXlaLdXn4+0hJH6lIscotp6ufVpJd1nxy4/4lWZml fD/vLXsPAhBbSYdWlXQ+DvRHMzdjGjDCTJNE7mgkR/YyEdhE8ZG2fAHEkPJ9Xi3CRB3K e6gN7kvl+4d9iKeNrvOlVGULxz+YmvWAnKAlXIVZa6w8KZePi/TJDhIL1JkgTCgXOA8G xIBVhfJp4Mm3963I0zk7K5JbEN3iwh0gIr9IUwrhtP+4TqC4S/wa1nK9pfLHqF0JRAyt bw5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=A4IlQeuqiYsDQ4SAUvSOxD4U847D4YvgodIGA6E77gc=; b=VL5P3GSYcRGPqzrDyAlfiqF2sCWilZ4jdHAo0JpRL/8xramv8+kmbM3RZfQkiLTWxH Ta2oeyfDe4FLa5Pfv5O3yUhNmrr1P3ZHEDxBfMGHtZUAhFKmWnb5iDTzZF7n6Yhg0OIn i8CSQOyhI5wK5mLvgItaOxCxz9Kx//CCL83jJMruJQ5uIo48nzF1l2VU2h/PTaMgI4WB Aw9qvURtbQjTn/5Kg3Q36gZqR1ix++KdLMc7K/EV6/275MKeQRj3UVo3PRQcTmdJ0MwX ASepTw9ZgVt5uhCn1fMyN3j25qpubrbcRet+NXjel3ouDf1rnG3yyQK85v+XuOf8EWsv f3dw== X-Gm-Message-State: APf1xPDTZLx2ygWIRS5TdEQaNO+xN10hB/tlkk7PdhqGPy9Tm8XkhYvy RIsc5HzECaUmVtYP8riWwFLj5SZWapehskx11NY= X-Google-Smtp-Source: AG47ELu2yP0uDJM3HY9s8/trMNgFRSq+EpbSXy5XuNvfDqEygAdLT1SLIpN+sjH9qmG4gD2e8UwS0h6BZwp9kBAjfcc= X-Received: by 10.176.24.161 with SMTP id t33mr19577386uag.198.1520517243505; Thu, 08 Mar 2018 05:54:03 -0800 (PST) MIME-Version: 1.0 Sender: etnapierala@gmail.com Received: by 10.176.7.2 with HTTP; Thu, 8 Mar 2018 05:54:03 -0800 (PST) In-Reply-To: References: <201802261411.w1QEBRt1002026@higson.cam.lispworks.com> <5A9A4B1E.8070206@anarchy.in.the.ph> <20180303113306.GB2029@brick> From: Edward Napierala Date: Thu, 8 Mar 2018 13:54:03 +0000 X-Google-Sender-Auth: cj0rPg62bAGGl7Dvy-Ike4BFAdo Message-ID: Subject: Re: growfs only works on GPT partitioning schemes? To: Mars G Miro Cc: Warner Losh , Martin Simmons , FreeBSD FS Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Thu, 08 Mar 2018 13:54:05 -0000 2018-03-03 15:29 GMT+00:00 Mars G Miro : > On Sat, Mar 3, 2018 at 7:33 PM, Edward Tomasz Napiera=C5=82a > wrote: > >> On 0303T1513, Mars G. Miro wrote: >> > On 02/26/18 22:30, Warner Losh wrote: >> > > >> > > On Mon, Feb 26, 2018 at 7:11 AM, Martin Simmons > > > > wrote: >> > > >> > > >>>>> On Mon, 26 Feb 2018 11:55:10 +0800, Mars G Miro said: >> > > > >> > > > It seems that growfs only works on GPT partitioned schemes = ? >> > > > >> > > > When I first installed my FreeBSD, I unfortunately chose BS= D >> during the >> > > > FS creation. Now that I ran out of space, I wanted to increase >> the >> > > > filesystem size. Successfully did so in Virtualbox but after >> rebooting, the >> > > > HD doesn't see the new allocated space. It has another virtual >> HD, one >> > > > created with GPT and I was able to increase it via growfs. >> > > >> > > For the BSD scheme, I think you also have to resize the slice >> (i.e. >> > > the MBR >> > > entry) and then resize the BSD partition within the slice. >> > > >> > > >> > > You do. The /etc/rc.d script that does resize on boot does that >> > > automatically, but we have no other automation for the process. >> > > >> > > Warner >> > >> > You guys have any idea how to resize the slice ? >> > >> > I have 2 HDs, both have already been increased (in VirtualBox). The BS= D >> > partitioned scheme below doesn't see the newly allocated disk space, >> > only the GPT one. >> > >> > camcontrol reprobe / gpart recover / etc doesn't do anything. >> > >> > mars@fbsd11vm1:~ % gpart show >> > =3D> 0 83886080 ada0 BSD (40G) >> > 0 4194304 1 freebsd-ufs (2.0G) >> > 4194304 16777216 2 freebsd-ufs (8.0G) >> > 20971520 62914559 4 freebsd-ufs (30G) >> > 83886079 1 - free - (512B) >> > >> > =3D> 40 104857520 ada1 GPT (60G) [CORRUPT] >> > 40 12582912 1 freebsd-swap (6.0G) >> > 12582952 92274608 2 freebsd-ufs (44G) >> >> What does "geom disk list" show? >> >> > > Supposedly the first drive should already have been 80Gb but: > > mars@fbsd11vm1:~ % geom disk list > ... > Geom name: ada0 > Providers: > 1. Name: ada0 > Mediasize: 42949672960 (40G) > Sectorsize: 512 > Mode: r3w3e6 > descr: VBOX HARDDISK > ident: VB1e5e1cab-a4c47c87 > rotationrate: 0 > fwsectors: 63 > fwheads: 16 > > Geom name: ada1 > Providers: > 1. Name: ada1 > Mediasize: 64424509440 (60G) > Sectorsize: 512 > Mode: r2w2e3 > descr: VBOX HARDDISK > ident: VBef5bd266-afbdd2b4 > rotationrate: 0 > fwsectors: 63 > fwheads: 16 > Okay, so this explains why you can't resize the partition: it's not the partitioning scheme, but the actual device size. Does a reboot make "geom disk list" show expected sizes? If not, what does a "dmesg | grep ada" show?