On Thu, 26 Apr 2018, Alexander Pyhalov wrote:
; It is related to cloning zones.
; I have a reproducible example.
;
; ...
; ioctl(6, ZFS_IOC_PROMOTE, 0x08045978) Err#2 ENOENT
; ...
;
I think this is related to permissions since promoting the dataset
would also require access to the source zone dataset..
root@zone2:~# zfs promote rpool/zone/zone2/ROOT/zbe-2
cannot promote 'rpool/zone/zone2/ROOT/zbe-2': dataset does not exist
It seems that if you go to the GZ and create and activate a BE there, then
it works from then on.
r151026# beadm create test
Created successfully
r151026# beadm activate test
Activated successfully
r151026# beadm destroy -F test
Destroyed successfully
r151026# zlogin zone2
root@zone2:~# beadm create zbe-2
Created successfully
root@zone2:~# beadm activate zbe-2
Activated successfully
but no longer in the clone source zone...
Did this ever work? It seems that when the zone datasets are related like
this then you need to stick to managing BEs in the GZ.
Andy
--
Citrus IT Limited | +44 (0)333 0124 007 | [email protected]
Rock House Farm | Green Moor | Wortley | Sheffield | S35 7DQ
Registered in England and Wales | Company number 4899123
------------------------------------------
illumos: illumos-discuss
Permalink:
https://illumos.topicbox.com/groups/discuss/discussions/T00ccd97df9cb1d97-M1373fdf4a3576a26cb1471e7
Delivery options: https://illumos.topicbox.com/groups
