Some notes on RootOnZFS article in wiki
Scot Hetzel
swhetzel at gmail.com
Mon Dec 21 16:45:46 UTC 2009
On 12/21/09, Mel Flynn <mel.flynn+fbsd.current at mailing.thruhere.net> wrote:
> > > 4) The given mount points have sane defaults, however, I use cvs to
> > > checkout
> > > the ports. It would be nice to have one example where data is already in
> > > a directory tree and how one can promote it to a zfs filesystem with
> > > special properties.
> >
> > You cant really promote something to a file system. The ideal situation is
> > you create the fs before you unpack the ports tar ball (or cvs). Otherwise,
> > rename /usr/ports (/usr/ports.old/, create the fs as desired, then rsync
> > the files there (or cp, or mv). Then delete the old tree.
>
>
> Right, I was wondering if that would actually work. If I do for example:
> zfs create -o compression=on zroot/usr/local/etc
>
> with files in there, would this result in the files being 'below' the mount
> point or would they be forever lost?
>
I just tried this and this is the result of creating a zfs filesystem
that mounts to the same location as an existing directory:
dv8t01# zfs list | grep local
dv8t01# ls /usr/local
Adobe include lib32 man src
bin info libdata modules translations
diablo-jdk1.6.0 kde4 libexec sbin www
etc lib live share
dv8t01# zfs create -o compression=on zroot/usr/local
dv8t01# ls /usr/local
dv8t01# zfs umount zroot/usr/local
dv8t01# ls /usr/local
Adobe include lib32 man src
bin info libdata modules translations
diablo-jdk1.6.0 kde4 libexec sbin www
etc lib live share
dv8t01# zfs destroy zroot/usr/local
Nothing was lost.
Scot
More information about the freebsd-current
mailing list