Daniel O'Connor wrote:
> On Thu, 2002-08-15 at 17:04, Patrick Thomas wrote:
> > Any suggestions on how to expand that file without doing the dump/restore
> > steps ?
>
> man 8 growfs perchance? :)
You can unmount it, grow the underlying file with:
dd if-/dev/zero bs=XXX,count=XXX >> filename
and *THEN* use growfs(8) on it.
Doing this will leave the allocation layout in the same state
that it is at present, so the bottom half of the FS will end
up fragmented, even though there is free space at the top (FS
growing does not equally redistribute the FS content into the
newly enlarged space).
The best approach is the same as it would be for a device:
dump and restore the FS from the old image to the new. In
the vn device case, you could just create a new empty FS of
the necessary size, and dump from the old piped to a restore
of the new.
If you can live with the internal fragmentation, use growfs(8);
if you can't, use dump/restore. IMO, you will have less
potential for future problems if you use dump/restore.
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
