From owner-freebsd-arm@FreeBSD.ORG Sun May 24 06:20:35 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 80A639EB for ; Sun, 24 May 2015 06:20:35 +0000 (UTC) Received: from monday.kientzle.com (kientzle.com [142.254.26.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CAE412BA for ; Sun, 24 May 2015 06:20:35 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id t4O5pOQN002547; Sun, 24 May 2015 05:51:24 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.105] (192.168.1.65 [192.168.1.65]) by kientzle.com with SMTP id g6xpwmvea5f2z87xkzpj3nn4ia; Sun, 24 May 2015 05:51:24 +0000 (UTC) (envelope-from tim@kientzle.com) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) Subject: Re: Possible growfs regression on r280862: Tue Mar 31/PANDABOARD snapshot From: Tim Kientzle In-Reply-To: <551EE431.10408@callfortesting.org> Date: Sat, 23 May 2015 22:51:23 -0700 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <493109F5-4ECB-463F-BD1C-A737CA38BE3A@kientzle.com> References: <551EE431.10408@callfortesting.org> To: Michael Dexter X-Mailer: Apple Mail (2.2098) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 May 2015 06:20:35 -0000 > On Apr 3, 2015, at 12:04 PM, Michael Dexter = wrote: >=20 >=20 > Hello all, >=20 > 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 . . . >=20 > [root@pcbsd] /root/snapshots# gpart resize -i 2 md1 > md1s2 resized > [root@pcbsd] /root/snapshots# gpart show md1 > =3D> 63 8388545 md1 MBR (4.0G) > 63 4095 1 !12 [active] (2.0M) > 4158 8384450 2 freebsd (4.0G) >=20 > [root@pcbsd] /root/snapshots# growfs /dev/md1s2a You=E2=80=99ve resized md1s2 but now have to =E2=80=98gpart resize=E2=80=99= md1s2a before you can growfs it. No, this is not obvious, which is why it=E2=80=99s 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