It's late and I typoed, that rpool/export/share example should have been
install
zfs set sharenfs='ro,anon=0' rpool/export/install
Leslie H Wood wrote, On 10/01/09 18:51:
keithk wrote, On 10/01/09 18:07:
Hi:
I am a newbie with zfs, so I apologize if I did no look deep enough
before posting. I am trying to create a zfs filesystem so I can take
snapshots of the file system. So, I create a file system like this:
rpool/export/vm 44.7G 744G 19.7G /export/vm
rpool/export/vm/linux 3.76G 744G 21K /export/vm/linux
rpool/export/vm/linux/ubuntu00 3.76G 744G 3.31G
/export/vm/linux/ubuntu00
As you can see, I have created 3 filesystems instead of just the
rpool/export/vm/linux/ubuntu00 because I use the following command to
create this filesystem:
zfs -p rpool/export/vm/linux/ubuntu00
Could I have create rpool/export/vm/linux/ubuntu00 without the 2
extra rpool/export/vm and rpool/export/vm/linux? It seems like there
are redundant filesystems created and mounted in this case.
They are actually datasets in ZFS and no the result is expected. It
has the advantage of letting you apply ZFS properties specifically to
any point in the tree. For exaple you might have an install
directory that would be shared with " zfs set sharenfs='ro,anon=0'
rpool/export/share" whcih you would not want to be applied to
rpool/export/vm. Loak at "man zfs" for all the properties.
rpool/export/install
rpool/export/vm
You could also use datasets just to the level above export and use
mkdir after that. For user home directories it is recommended to
use a dataset for each home directory.
...Les
Thanks.
_______________________________________________
opensolaris-help mailing list
opensolaris-help@opensolaris.org
_______________________________________________
opensolaris-help mailing list
opensolaris-help@opensolaris.org
