Darren;
Ahhhh.... zfs send | zfs receive onto the same filesystem???
er... I tried the following...
#zfs snapshot myplace/myd...@prededup
The above created the following...
ad...@sunlight:~$ zfs list -t snapshot -r myplace/mydata
NAME USED AVAIL REFER MOUNTPOINT
myplace/myd...@scriptsnap1 675K - 289M -
myplace/myd...@scriptsnap2 675K - 289M -
myplace/myd...@scriptsnap3 476K - 289M -
myplace/myd...@prededup 0 - 289M - <---- Snapshot
created manually
ad...@sunlight:~$
The snapshots named scriptsnap was created by a rotating zfs snapshot
script i wrote, one which i CRON to run every night...
er... then..
r...@sunlight:/root# zfs send myplace/myd...@prededup | zfs receive -v
myplace/mydata
cannot receive new filesystem stream: destination 'myplace/fujitsu' exists
must specify -F to overwrite it
r...@sunlight:/root# zfs send myplace/myd...@prededup | zfs receive -Fv
myplace/mydata
cannot receive new filesystem stream: destination has snapshots (eg.
myplace/myd...@scriptsnap3)
must destroy them to overwrite it
Could you advice....
I am guessing I must destroy all related snapshots first?
Warmest Regards
Steven Sim
Darren J Moffat wrote:
Steven Sim wrote:
Hello;
How do we dedup existing data?
Currently by running a zfs send | zfs recv.
Will a ZFS send to an output file in a temporary staging area in the
same pool and a subsequent reconstruct (zfs receive) from the file be
sufficient?
Yes but you can avoid the temp file and just do zfs send | zfs recv.
Or do I have to completely move the data out of the pool and back in
again?
That is what zfs send and recv actually does.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
