On 08/14/16 03:08 PM, Humberto Ramirez wrote:
joyent_20151210T194528Z
While playing with zones I encounter the following issue:
I cloned a zone via zfs clone, I then promoted the resulting file
system with 'zfs promote' (no good reasoning behind this decision)
It looks like you cloned an image, not a zone.
After destroying a zone via vmadm destroy, the file system remains and
I'm unable to destroy it
The zone I cloned was based on Joyent image 842e6fa6-6e9b-11e5-8402-1b490459e334
The cloned zone is 235463b2-67b4-e224-bd17-b62b6cbf99eb
How did you clone it?
image 842e6fa6-6e9b-11e5-8402-1b490459e334 has since disappeared from
the list of available images
can someone make sense of what happened ?
# zfs get origin zones/235463b2-67b4-e224-bd17-b62b6cbf99eb
NAME PROPERTY VALUE
SOURCE
zones/235463b2-67b4-e224-bd17-b62b6cbf99eb origin
zones/842e6fa6-6e9b-11e5-8402-1b490459e334@final -
# zfs promote zones/235463b2-67b4-e224-bd17-b62b6cbf99eb
# zfs get origin zones/235463b2-67b4-e224-bd17-b62b6cbf99eb
NAME PROPERTY VALUE SOURCE
zones/235463b2-67b4-e224-bd17-b62b6cbf99eb origin - -
# zfs list |grep 2354
zones/235463b2-67b4-e224-bd17-b62b6cbf99eb 203M 9.95T 26K
/zones/235463b2-67b4-e224-bd17-b62b6cbf99eb
# zfs list -t snapshot |grep 2354
zones/235463b2-67b4-e224-bd17-b62b6cbf99eb@final
5.32M - 184M -
zones/235463b2-67b4-e224-bd17-b62b6cbf99eb@20160813
19.2M - 198M -
Thus far the clone now owns the snapshots from the origin filesystem
which is now the child. This was a bad idea: the image filesystem is no
a clone so it can't be used as an image.
# zfs destroy zones/235463b2-67b4-e224-bd17-b62b6cbf99eb
cannot destroy 'zones/235463b2-67b4-e224-bd17-b62b6cbf99eb':
filesystem has children
use '-r' to destroy the following datasets:
zones/235463b2-67b4-e224-bd17-b62b6cbf99eb@20160813
zones/235463b2-67b4-e224-bd17-b62b6cbf99eb@final
Did you try with -r? It would probably have to you that you also need
-R to remove the child clone.
# zfs destroy zones/f9671930-852b-4d9d-b89f-d8aaa001a648
cannot unmount '/zones/f9671930-852b-4d9d-b89f-d8aaa001a648': Device busy
cannot unmount '/zones/f9671930-852b-4d9d-b89f-d8aaa001a648': Device busy
Where does this filesystem come into the picture?
# imgadm list
UUID NAME VERSION OS
PUBLISHED
235463b2-67b4-e224-bd17-b62b6cbf99eb - - - -
I've never seen this before, but I'm guessing it is the result of the
earlier promotion.
3766d58c-d777-11e1-89c1-4fa1b8ed5c1e base 1.7.1
smartos 2012-07-27T00:18:34Z
3882b5da-b0e8-11e2-b3a9-dbcf26c3e051 percona 13.1.0
smartos 2013-05-01T20:07:28Z
d34c301e-10c3-11e4-9b79-5f67ca448df0 base64 14.2.0
smartos 2014-07-21T10:43:17Z
0a90f47c-497e-11e4-9451-bfbecae680a8 debian-7 20141001
linux 2014-10-01T15:17:21Z
8124986e-618e-11e4-912e-afd574ea711e leofs 1.1.5
smartos 2014-11-01T08:22:41Z
5a4ba06a-c1bb-11e4-af0b-4be0ce4ce04c minimal-64-lts 14.4.0
smartos 2015-03-03T15:38:34Z
818cc79e-ceb3-11e4-99ee-7bc8c674e754 lx-ubuntu-14.04 20150320
other 2015-03-20T03:45:09Z
#
# imgadm import 842e6fa6-6e9b-11e5-8402-1b490459e334
Image 842e6fa6-6e9b-11e5-8402-1b490459e334 (base-64 15.3.0) is already
installed, skipping
Oops....
# vmadm list
UUID TYPE RAM STATE ALIAS
9ef59fc8-6fdd-4c6e-82cf-441af62b0c24 OS 256 stopped -
9652418f-a059-eb30-9024-de07910b0fb0 OS 700 running OpenVPN-1
a9d90fa8-69b6-c6fc-bf82-9d89165fb370 OS 1024 running samba01
dd9977dd-26b2-49d7-b6b5-0a74a414d4a2 KVM 1024 stopped
test-kvm-01
#
How do these relate to the filesystems above?
--
Ian.
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
