hello all, i guess i hit the bug: http://defect.opensolaris.org/bz/show_bug.cgi?id=7491 on my system: # zfs list rpool/zones/catalogue3 NAME USED AVAIL REFER MOUNTPOINT rpool/zones/catalogue3 10.1G 7.17G 70K /zones/catalogue3 # zfs destroy rpool/zones/catalogue3 cannot destroy 'rpool/zones/catalogue3': filesystem has children use '-r' to destroy the following datasets: rpool/zones/catalogue3/ROOT/z...@20100709 rpool/zones/catalogue3/ROOT/zbe rpool/zones/catalogue3/ROOT/zb...@catalogue_snap rpool/zones/catalogue3/ROOT/zb...@catalogue2_snap rpool/zones/catalogue3/ROOT/zb...@test_drupal_snap ....
and: # zfs destroy -r rpool/zones/catalogue3 cannot destroy 'rpool/zones/catalogue3': filesystem has dependent clones use '-R' to destroy the following datasets: rpool/zones/bibcmi4/ROOT/zb...@bibcmi3_snap rpool/zones/template_zone/ROOT/z...@20100709 rpool/zones/template_zone/ROOT/zbe rpool/zones/template_zone/ROOT/zb...@zbe-2 rpool/zones/template_zone/ROOT/zb...@20100709 rpool/zones/template_zone/ROOT/zbe-2 rpool/zones/bibcmi4/ROOT/zb...@bibcmi_snap rpool/zones/bibcmi/ROOT/z...@20100709 rpool/zones/bibcmi/ROOT/zbe rpool/zones/bibcmi/ROOT/zb...@zbe-2 ... i just want to destroy catalogue3 zone, not the others. So according the last command, i manually promote the corresponding dataset: # zfs promote rpool/zones/bibcmi4/ROOT/zbe-2 # zfs promote rpool/zones/catalogue4/ROOT/zbe etc... But now, is it possible to find all the fs that have dependant clones? (i have 17 zones, many of them created as clones). I guess that every promote command consumes more place on rpool? that's what prevent me to upgrade to b134 now, i have to clean the disk before upgrade. thanks in advance for help, gerard -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
