Chad J. Milios
milios at ccsys.com
Sun Sep 27 02:23:06 UTC 2015
> On Sep 26, 2015, at 9:03 PM, William A. Mahaffey III <wam at hiwaay.net> wrote:
> As an aside, is there a way to configure the stick's FS to use/report all available space, rather than what the img was sized to, *after* dd-ing the img ?
> [root at 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% /usr
> /dev/stripe/home_str ufs 3684793728 220043372 3169966860 6% /home
> procfs procfs 4 4 0 100% /proc
> tmpfs tmpfs 8388608 32 8388576 0% /tmp
> 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 at kabini1, /etc, 8:09:52pm] 343 %
> i.e. /media/sd shows about 698 MiB instead of full 4-ish MB it is really sized to .... TIA for any clues :-).
> William A. Mahaffey III
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 partition must be expanded first using one or more incantations of gpart, bsdlabel and/or fdisk in some particular order. Looks like you'd be using just bsdlabel for your case.
Note that in the case of UFS certain parameters are chosen at creation time that make growing more than an order of magnitude possibly suboptimal compared to a dump/restore. In your case I wouldn't worry about that.
More information about the freebsd-questions