[pve-devel] nexenta plugin question

Michael Rasmussen mir at datanom.net
Fri May 24 16:51:30 CEST 2013

On Fri, 24 May 2013 14:22:45 +0000
Dietmar Maurer <dietmar at proxmox.com> wrote:

> I have a VM 105 using a single disk on nexenta storage:
> # pvesm list nex1
> nex1:vm-105-disk-1   raw 1073741824 105
> After I convert to template I get:
> # pvesm list nex1
> nex1:vm-105-disk-1                   raw 1073741824 105
> nex1:vm-105-disk-1/base-105-disk-1   raw 1073741824 105
> I thought we should hide the original volume? Also, It should not be
> possible to delete "nex1:vm-105-disk-1"?
This is something nexenta specific since nexenta does not provide a
volume rename. Since other solaris based distribution provides this
feature it is more clean in the zfsplugin:
nex1:vm-105-disk-1     raw 1073741824 105
nex1:base-105-disk-1   raw 1073741824 105

Also since the clone is a real zfs clone deleting nex1:vm-105-disk-1
will fail with the message: Cannot delete nex1:vm-105-disk-1 because of
depending clones. So to delete nex1:vm-105-disk-1 will require deletion
of nex1:base-105-disk-1 first.

Michael Rasmussen

Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
mir <at> datanom <dot> net
mir <at> miras <dot> org
Hodie natus est radici frater.

[ Unto the root is born a brother ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://pve.proxmox.com/pipermail/pve-devel/attachments/20130524/20826edb/attachment.pgp>

More information about the pve-devel mailing list