Hi Tester,
It is difficult for me to see all that is going on here. Can you provide
the steps and the complete output?
I tried to reproduce this on latest Nevada bits and I can't. The
snapshot sizing looks correct to me after a snapshot/clone promotion.
Thanks,
Cindy
# zfs create tank/fs1
# mkfile 100m /tank/fs1/f1
# zfs list tank
NAME USED AVAIL REFER MOUNTPOINT
tank 100M 134G 23K /tank
# zfs snapshot tank/f...@now
# zfs clone tank/f...@now tank/fsnew
# zpool set listsnapshots=on tank
# zfs list -r tank
NAME USED AVAIL REFER MOUNTPOINT
tank 100M 134G 24K /tank
tank/fs1 100M 134G 100M /tank/fs1
tank/f...@now 0 - 100M -
tank/fsnew 0 134G 100M /tank/fsnew
The newly promoted file system is charged the
USED space.
# zfs promote tank/fsnew
# zfs list -r tank
NAME USED AVAIL REFER MOUNTPOINT
tank 100M 134G 24K /tank
tank/fs1 0 134G 100M /tank/fs1
tank/fsnew 100M 134G 100M /tank/fsnew
tank/fs...@now 0 - 100M -
On 02/10/10 14:06, tester wrote:
Hello,
Immediately after a promote, the snapshot of the promoted clone has 1.25G used.
NAME USED AVAIL REFER
q2/fs1 4.01G 9.86G 8.54G
q2/f...@test1 [b]1.25G[/b] - 5.78G -
prior to the promote the snapshot of the origin file system looked like this
NAME USED AVAIL REFER
q2/fs1-o1 5.81G 9.86G 5.78G
q2/fs1...@test1 33.2M - 5.78G -
Where is q2/f...@test1 picking 1.25G from?
Thanks
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
