Date: Thu, 8 Mar 2018 13:54:03 +0000 From: Edward Napierala <trasz@freebsd.org> To: Mars G Miro <spry@anarchy.in.the.ph> Cc: Warner Losh <imp@bsdimp.com>, Martin Simmons <martin@lispworks.com>, FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: growfs only works on GPT partitioning schemes? Message-ID: <CAFLM3-qVQzYhMnhO%2B%2BpK0Dde1GO59okuNd-p2DPOrhLnONHBJA@mail.gmail.com> In-Reply-To: <CADRRZErLXt4Mw%2B_dmsF2q=apy_2HXR6UMtF=ur1Pn=6bnCwD5w@mail.gmail.com> References: <CADRRZEr%2BaggE3MHNK9DA6f1Jq9T=buNqiRy2Z%2B5N7=N%2BR_PAWA@mail.gmail.com> <201802261411.w1QEBRt1002026@higson.cam.lispworks.com> <CANCZdfrSy4N7dXj%2BNRHuCeUj1Fp3xm2_T06BvpCpL3qRsGSS-A@mail.gmail.com> <5A9A4B1E.8070206@anarchy.in.the.ph> <20180303113306.GB2029@brick> <CADRRZErLXt4Mw%2B_dmsF2q=apy_2HXR6UMtF=ur1Pn=6bnCwD5w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2018-03-03 15:29 GMT+00:00 Mars G Miro <spry@anarchy.in.the.ph>: > On Sat, Mar 3, 2018 at 7:33 PM, Edward Tomasz Napiera=C5=82a <trasz@freeb= sd.org > > 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 <martin@lispworks.co= m >> > > <mailto:martin@lispworks.com>> 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFLM3-qVQzYhMnhO%2B%2BpK0Dde1GO59okuNd-p2DPOrhLnONHBJA>