Date: Mon, 4 Feb 2013 06:24:43 +0700 From: Erich Dollansky <erichsfreebsdlist@alogt.com> To: Tim Kientzle <kientzle@freebsd.org> Cc: freebsd-current Current <freebsd-current@freebsd.org> Subject: Re: gpart resize vs. cache? Message-ID: <20130204062443.485cff60@X220.ovitrap.com> In-Reply-To: <3D812191-2D6E-43B2-B9C1-F00FFA44C5F8@freebsd.org> References: <3D812191-2D6E-43B2-B9C1-F00FFA44C5F8@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Sun, 3 Feb 2013 12:06:41 -0800 Tim Kientzle <kientzle@freebsd.org> wrote: > I'm tinkering with a disk image that automatically > fills whatever media you put it onto. But I'm having > trouble with gpart resize failing. > > Disk layout: > MBR with two slices mmcsd0s1 and mmcsd0s2 > bsdlabel with one partition mmcsd0s2a > > Before I can use growfs, I have two gpart resize operations: > > 1) gpart resize -i 2 mmcsd0 > > 2) gpart resize -i 1 mmcsd0s2 > > Step 1 resizes mmcsd0s2 and always succeeds. > > Step 2 resizes mmcsd0s2a and always fails > with "No space on device." > I used a gpart show between in a different situation. The script did not work without it. When I entered the same commands from the command line, they all worked. So, things could be related to cache or delayed writes. Erich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130204062443.485cff60>