Date: Fri, 9 Mar 2018 15:03:06 +0800 From: Mars G Miro <spry@anarchy.in.the.ph> To: Martin Simmons <martin@lispworks.com>, =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= <trasz@freebsd.org> Cc: Warner Losh <imp@bsdimp.com>, FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: growfs only works on GPT partitioning schemes? Message-ID: <CADRRZEp6HSUiApi431B17UUF1q6LAj8Fav3EfyMN8RQ625bs2g@mail.gmail.com> In-Reply-To: <201803081426.w28EQNE6003598@higson.cam.lispworks.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> <CAFLM3-qVQzYhMnhO%2B%2BpK0Dde1GO59okuNd-p2DPOrhLnONHBJA@mail.gmail.com> <201803081426.w28EQNE6003598@higson.cam.lispworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 8, 2018 at 10:26 PM, Martin Simmons <martin@lispworks.com> wrote: > >>>>> On Thu, 8 Mar 2018 13:54:03 +0000, Edward Napierala said: > > > > 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@freebsd.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.com > > >> > > <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 chos= e > 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 aft= er > > >> 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 slic= e > > >> (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). Th= e > BSD > > >> > partitioned scheme below doesn't see the newly allocated disk spac= e, > > >> > 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. > > > The actual size is already increased in Virtualbox but the FreeBSD BSD partitioned HD does not see it. The second GPT partitioned HD did not have problems (I was able to growfs it). > > Does a reboot make "geom disk list" show expected sizes? If not, > > what does a "dmesg | grep ada" show? > > I've rebooted it many times. See more below. > Also, check the size using "vboxmanage showhdinfo" on the host and check > that > the virtual disk doesn't have any vbox snapshots. > > __Martin > It does have 2 snapshots in fact, this is a known problem ? root@fbsd11z51vm1:~ # gpart list Geom name: ada0 modified: false state: OK fwheads: 16 fwsectors: 63 last: 83886079 first: 0 entries: 8 scheme: BSD Providers: 1. Name: ada0a Mediasize: 2147483648 (2.0G) Sectorsize: 512 Mode: r1w1e1 rawtype: 7 length: 2147483648 offset: 0 type: freebsd-ufs index: 1 end: 4194303 start: 0 2. Name: ada0b Mediasize: 8589934592 (8.0G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 2147483648 Mode: r1w1e1 rawtype: 7 length: 8589934592 offset: 2147483648 type: freebsd-ufs index: 2 end: 20971519 start: 4194304 3. Name: ada0d Mediasize: 32212254720 (30G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 2147483648 Mode: r1w1e1 rawtype: 7 length: 32212254720 offset: 10737418240 type: freebsd-ufs index: 4 end: 83886079 start: 20971520 Consumers: 1. Name: ada0 Mediasize: 42949672960 (40G) Sectorsize: 512 Mode: r3w3e6 Geom name: ada1 modified: false state: OK fwheads: 16 fwsectors: 63 last: 125829079 first: 40 entries: 152 scheme: GPT Providers: 1. Name: ada1p1 Mediasize: 6442450944 (6.0G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 20480 Mode: r1w1e0 rawuuid: 1a11b419-f839-11e7-9145-080027d107ad rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: (null) length: 6442450944 offset: 20480 type: freebsd-swap index: 1 end: 12582951 start: 40 2. Name: ada1p2 Mediasize: 57982017536 (54G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 2147504128 Mode: r1w1e1 rawuuid: 288ccc2c-f839-11e7-9145-080027d107ad rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b label: (null) length: 57982017536 offset: 6442471424 type: freebsd-ufs index: 2 end: 125829079 start: 12582952 Consumers: 1. Name: ada1 Mediasize: 64424509440 (60G) Sectorsize: 512 Mode: r2w2e3 root@fbsd11z51vm1:~ # dmesg -a | grep ^ada ada0 at ata0 bus 0 scbus0 target 0 lun 0 ada0: cd0: <VBOX HARDDISK 1.0> ATA8-ACS device ada0: Serial Number VB1e5e1cab-a4c47c87 ada0: 16.700MB/s transferscd0: 16.700MB/s transfers ( (WDMA2, ATAPI 12bytes, PIO 65534bytes)WDMA2, ada0: 40960MB (83886080 512 byte sectors) ada1 at ata0 bus 0 scbus0 target 1 lun 0 ada1: <VBOX HARDDISK 1.0> ATA8-ACS device ada1: Serial Number VBef5bd266-afbdd2b4 ada1: 16.700MB/s transfers (WDMA2, PIO 65536bytes) ada1: 61440MB (125829120 512 byte sectors) root@fbsd11z51vm1:~ # 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) Thanks all! --=20 cheers mars -----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADRRZEp6HSUiApi431B17UUF1q6LAj8Fav3EfyMN8RQ625bs2g>