Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 26 Sep 2015 22:23:03 -0400
From:      "Chad J. Milios" <milios@ccsys.com>
To:        "William A. Mahaffey III" <wam@hiwaay.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: dd question
Message-ID:  <CE54A645-7EC9-4E8F-8C03-98BAE3D79986@ccsys.com>
In-Reply-To: <560740C7.3060102@hiwaay.net>
References:  <5606A4FF.4090105@hiwaay.net> <CA%2BtpaK3UOEfKSfSjbdcH%2BR2jaU9=XVBEg%2B%2Bjn5VCbiiUkLF_Tg@mail.gmail.com> <56073D71.5060404@sneakertech.com> <560740C7.3060102@hiwaay.net>

next in thread | previous in thread | raw e-mail | index | archive | help
> On Sep 26, 2015, at 9:03 PM, William A. Mahaffey III <wam@hiwaay.net> wrot=
e:
>=20
> ...
> As an aside, is there a way to configure the stick's FS to use/report all a=
vailable space, rather than what the img was sized to, *after* dd-ing the im=
g ?
>=20
>=20
> [root@kabini1, /etc, 8:09:41pm] 342 % df
> Filesystem            Type      1024-blocks      Used      Avail Capacity =
 Mounted on
> /dev/ada0p3           ufs          20307196  12140912    6541712 65%    /
> devfs                 devfs               1         1          0 100%    /=
dev
> /dev/stripe/usr_str   ufs          60921596  10477380   45570492 19%    /u=
sr
> /dev/stripe/home_str  ufs        3684793728 220043372 3169966860 6%    /ho=
me
> procfs                procfs              4         4          0 100%    /=
proc
> tmpfs                 tmpfs         8388608        32    8388576 0%    /tm=
p
> linprocfs             linprocfs           4         4          0 100%    /=
compat/linux/proc
> fdescfs               fdescfs             1         1          0 100%    /=
dev/fd
> /dev/da0a             ufs            698671    651741      -8963 101%    /=
media/sd
> [root@kabini1, /etc, 8:09:52pm] 343 %
>=20
>=20
> i.e. /media/sd shows about 698 MiB instead of full 4-ish MB it is really s=
ized to .... TIA for any clues :-).
>=20
> --=20
>=20
>    William A. Mahaffey III
>=20

growfs will do the deed for UFS filesystems. Use the -N flag to see what it'=
ll do without doing it. It may also be the case that the containing partitio=
n must be expanded first using one or more incantations of gpart, bsdlabel a=
nd/or fdisk in some particular order. Looks like you'd be using just bsdlabe=
l for your case.

Note that in the case of UFS certain parameters are chosen at creation time t=
hat make growing more than an order of magnitude possibly suboptimal compare=
d to a dump/restore. In your case I wouldn't worry about that.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CE54A645-7EC9-4E8F-8C03-98BAE3D79986>