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/fs1 at 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-o1 at test1 33.2M - 5.78G - Where is q2/fs1 at test1 picking 1.25G from? Thanks -- This message posted from opensolaris.org
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/fs1 at now # zfs clone tank/fs1 at 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/fs1 at 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/fsnew at 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/fs1 at 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-o1 at test1 33.2M - 5.78G - > > Where is q2/fs1 at test1 picking 1.25G from? > > Thanks
Hello, # /usr/sbin/zfs list -r rgd3 NAME USED AVAIL REFER MOUNTPOINT rgd3 16.5G 23.4G 20K /rgd3 rgd3/fs1 19K 23.4G 21K /app/fs1 rgd3/fs1-patch 16.4G 23.4G 16.4G /app/fs1-patch rgd3/fs1-patch at snap1 34.8M - 16.4G - # /usr/sbin/zfs promote rgd3/fs1 snap is 16.4G in USED. # /usr/sbin/zfs list -r rgd3 NAME USED AVAIL REFER MOUNTPOINT rgd3 16.5G 23.4G 20K /rgd3 rgd3/fs1 16.4G 23.4G 21K /app/fs1 rgd3/fs1 at snap1 16.4G - 16.4G - rgd3/fs1-patch 33.9M 23.4G 16.4G /app/fs1-patch 5.10 Generic_141414-10 I tired to line up numbers, it does not work. Sorry for the format. -- This message posted from opensolaris.org
Hi-- From your pre-promotion output, both fs1-patch and snap1 are referencing the same 16.4 GB, which makes sense. I don''t see how fs1 could be a clone of fs1-patch because it should be REFER''ing 16.4 GB as well in your pre-promotion zfs list. If you snapshot, clone, and promote, then the snapshot-->clone is promoted to be the origin file system and so is now charged the USED space, but the post-promotion snapshot space should remain in the REFER column. Try it yourself with a test file system, create a 100m file, snapshot, and clone. Then promote the clone. You will see that the 100MB in REFER space of the original snapshot becomes 100MB USED space in the newly promoted clone. The original snapshot remains 100MB in REFER. If the test snap/clone/promote works then we need to figure out what''s going on in your rgd3/fs* environment. From your output, it almost looks like the space accounting for snap1 and fs1 are reversed in your post- promotion zfs list. I don''t know why. I can''t reproduce this in the Solaris 10 10/09 release. Thanks, Cindy # zfs create tank/fs1 # mkfile 100m /tank/fs1/file1 # zfs list -r tank NAME USED AVAIL REFER MOUNTPOINT tank 100M 66.8G 23K /tank tank/fs1 100M 66.8G 100M /tank/fs1 # zfs snapshot tank/fs1 at snap1 # zfs clone tank/fs1 at snap1 tank/fs1-patch # zfs list -r tank NAME USED AVAIL REFER MOUNTPOINT tank 100M 66.8G 23K /tank tank/fs1 100M 66.8G 100M /tank/fs1 tank/fs1 at snap1 0 - 100M - tank/fs1-patch 0 66.8G 100M /tank/fs1-patch # zfs promote tank/fs1-patch # zfs list -r tank NAME USED AVAIL REFER MOUNTPOINT tank 100M 66.8G 24K /tank tank/fs1 0 66.8G 100M /tank/fs1 tank/fs1-patch 100M 66.8G 100M /tank/fs1-patch tank/fs1-patch at snap1 0 - 100M - On 02/12/10 19:37, tester wrote:> Hello, > > # /usr/sbin/zfs list -r rgd3 > NAME USED AVAIL REFER MOUNTPOINT > rgd3 16.5G 23.4G 20K /rgd3 > rgd3/fs1 19K 23.4G 21K /app/fs1 > rgd3/fs1-patch 16.4G 23.4G 16.4G /app/fs1-patch > rgd3/fs1-patch at snap1 34.8M - 16.4G - > > # /usr/sbin/zfs promote rgd3/fs1 > > snap is 16.4G in USED. > > # /usr/sbin/zfs list -r rgd3 > NAME USED AVAIL REFER MOUNTPOINT > rgd3 16.5G 23.4G 20K /rgd3 > rgd3/fs1 16.4G 23.4G 21K /app/fs1 > rgd3/fs1 at snap1 16.4G - 16.4G - > rgd3/fs1-patch 33.9M 23.4G 16.4G /app/fs1-patch > > 5.10 Generic_141414-10 > > I tired to line up numbers, it does not work. Sorry for the format.