Date: Sat, 23 May 2015 22:51:23 -0700 From: Tim Kientzle <tim@kientzle.com> To: Michael Dexter <editor@callfortesting.org> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Possible growfs regression on r280862: Tue Mar 31/PANDABOARD snapshot Message-ID: <493109F5-4ECB-463F-BD1C-A737CA38BE3A@kientzle.com> In-Reply-To: <551EE431.10408@callfortesting.org> References: <551EE431.10408@callfortesting.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Apr 3, 2015, at 12:04 PM, Michael Dexter <editor@callfortesting.org> wrote: > > > Hello all, > > I have been experimenting with the FreeBSD 11.0-CURRENT #0 r280130: Mon > Mar 16 and FreeBSD 11.0-CURRENT #0 r280862: Tue Mar 31 and I noticed > that the latter is not running growfs on boot. (It is also not reporting > the system's available memory at boot time.) Sorry for the late response. I believe this is fixed for Crochet-built images now. > I tried manually growing the filesystem using a memory device and while > the gpart resize went fine, the growfs would not work but I could easily > have the syntax wrong: . . . snip . . . > > [root@pcbsd] /root/snapshots# gpart resize -i 2 md1 > md1s2 resized > [root@pcbsd] /root/snapshots# gpart show md1 > => 63 8388545 md1 MBR (4.0G) > 63 4095 1 !12 [active] (2.0M) > 4158 8384450 2 freebsd (4.0G) > > [root@pcbsd] /root/snapshots# growfs /dev/md1s2a You’ve resized md1s2 but now have to ‘gpart resize’ md1s2a before you can growfs it. No, this is not obvious, which is why it’s nice to have it scripted into the system. ;-) > growfs: requested size 952MB is not larger than the current filesystem > size 952MB > [root@pcbsd] /root/snapshots# growfs -s 4G /dev/md1s2a > growfs: requested size 4.0GB is larger than the available 952MB Cheers, Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?493109F5-4ECB-463F-BD1C-A737CA38BE3A>