From owner-freebsd-fs@freebsd.org Sat Mar 3 11:33:10 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 01BA3F3338F for ; Sat, 3 Mar 2018 11:33:10 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (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 6E9027CB58 for ; Sat, 3 Mar 2018 11:33:09 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-wm0-x22a.google.com with SMTP id t74so7646811wme.3 for ; Sat, 03 Mar 2018 03:33:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=6YLobks9zfWkmQXf8NJ3FA5Zgq9kV0xCTAzuR7aXu+o=; b=QP4GSDf1/NCIRa0AFg+io1nFvpejMJylIrdYUVIvlW7ep9OvvYy8V7LC9XL73qSTFl qLjyqAZw7reK/I/q2MiZuPttDWS2ayTWSL8GyMgYjZZ5aIoeGXW3mJbiQyx3sFTqSV98 mmF6sEWRvQBBIfjewO/ZXHsS/CgMP233DnxH7QpsFdHRZkj9/0oX4fOT0w8sq9u9F03a F2BRzuydrMHxZz4XC1naqvZKCs3nGG31op+S3aD0AOHPqKyBqRtmIv24U9ibswzo7xSI zSvT8CVRstW//7rDuJO6RUl8dqKEWy96bg7rul+YVRtpaiwP8bpHcbbE54QPAAmIbLf8 w2xQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=6YLobks9zfWkmQXf8NJ3FA5Zgq9kV0xCTAzuR7aXu+o=; b=GzRiR0UUQTAObRyY1Oe2HbASlJ6xpOZwjhRjji3ptigtgKQjBN4tDizKCpog3qe1l1 F+Zqith+WKSbC4coqfwlSpMruFD+LYHZL7dNxMn6lM1BlClgpU+trBBfU8X3NRWpduUC gm5jDdavG9LPULlEG6v5xW8EWWxnTEMlI/l1Dx6IcP7xvbPTameGbU5ncGLR9s2CMQDH +UXolAKQbOS3Immkj9GRR+EGZy6YciTKgHKl4y2mtIX4isEII+ZF42C6ELacpYEvFd1C DSTx8Eo3QIZMJTMX9qdbjrcadSKkO/lE8nkr9G4QTAYreJUXcKmKyBWx1/795uMwJisq uzsQ== X-Gm-Message-State: AElRT7EebuUjurbOg9mCvj8y5jjANvuWfsqXEVGsWVK34lzIJ/DcmRzy c6RuoEwYSVKz3NpC6XVHO/I= X-Google-Smtp-Source: AG47ELuKYhVFUajxF99wlm1H6t4g/rP+Xz6W3EMc3HyNZnrO3nDKMA+MA5LjmnFiR2IZU+xCRXv11g== X-Received: by 10.28.74.199 with SMTP id n68mr3611035wmi.83.1520076788473; Sat, 03 Mar 2018 03:33:08 -0800 (PST) Received: from brick (cpc92302-cmbg19-2-0-cust461.5-4.cable.virginm.net. [82.1.209.206]) by smtp.gmail.com with ESMTPSA id v23sm298108wmc.22.2018.03.03.03.33.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 03 Mar 2018 03:33:07 -0800 (PST) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Sat, 3 Mar 2018 11:33:06 +0000 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: "Mars G. Miro" Cc: Warner Losh , Martin Simmons , FreeBSD FS Subject: Re: growfs only works on GPT partitioning schemes? Message-ID: <20180303113306.GB2029@brick> Mail-Followup-To: "Mars G. Miro" , Warner Losh , Martin Simmons , FreeBSD FS References: <201802261411.w1QEBRt1002026@higson.cam.lispworks.com> <5A9A4B1E.8070206@anarchy.in.the.ph> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5A9A4B1E.8070206@anarchy.in.the.ph> User-Agent: Mutt/1.9.3 (2018-01-21) 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: Sat, 03 Mar 2018 11:33:10 -0000 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 BSD 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 BSD > 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 > => 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) > > => 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?