Hi,
Recently i created a new dataset on an existing dataset on my FreeNAS server.
I did it in order to be able to take snapshots of a single directory, instead of the whole thing.
Original dataset: /nfs/dataset1
I've created in FreeNAS GUI: /nfs/dataset1/dataset2
afterwards i could see that a new directory named 'dataset2' was created at the root of dataset1.
I copied data into it. however i do not see the data is filling the new dataset (dataset2). it is still part of the top dataset (dataset1).
It looks, from the clientside that the new dataset2 isn't really pointing to the new dataset, instead to a normal directory (with the same name as dataset2) on dataset1.
from a client:
$ du -hc /mnt/dataset1/dataset2
104G
On the freeNAS Server:
$ df -h
Filesystem Size Used Avail Capacity Mounted on
nfs/dataset1 48T 25T 23T 51% /mnt/dataset1
nfs/dataset1/dataset2 23T 201K 23T 0% /mnt/dataset1/dataset2
Any idea how can i overcome this scenario?
- Moshe
Recently i created a new dataset on an existing dataset on my FreeNAS server.
I did it in order to be able to take snapshots of a single directory, instead of the whole thing.
Original dataset: /nfs/dataset1
I've created in FreeNAS GUI: /nfs/dataset1/dataset2
afterwards i could see that a new directory named 'dataset2' was created at the root of dataset1.
I copied data into it. however i do not see the data is filling the new dataset (dataset2). it is still part of the top dataset (dataset1).
It looks, from the clientside that the new dataset2 isn't really pointing to the new dataset, instead to a normal directory (with the same name as dataset2) on dataset1.
from a client:
$ du -hc /mnt/dataset1/dataset2
104G
On the freeNAS Server:
$ df -h
Filesystem Size Used Avail Capacity Mounted on
nfs/dataset1 48T 25T 23T 51% /mnt/dataset1
nfs/dataset1/dataset2 23T 201K 23T 0% /mnt/dataset1/dataset2
Any idea how can i overcome this scenario?
- Moshe