mmm, maybe, need to be tested. (my nexenta test box is down for now, I'll can test it not before friday).
I found an article here COMSTAR: Keeping GUID's with a new Backend Device https://www.illumos.org/boards/1/topics/639 it seem to be possible to specify the guid with stmfadm command (with ssh, and not the nexenta api, so I don't know if it's break the nexenta view of the luns) stmfadm create-lu -p guid=*LUN GUID* /dev/rdsk/... I'll tell the question to nexenta support. ----- Mail original ----- De: "Dietmar Maurer" <diet...@proxmox.com> À: "Alexandre DERUMIER" <aderum...@odiso.com> Cc: pve-devel@pve.proxmox.com Envoyé: Mercredi 19 Septembre 2012 08:02:19 Objet: RE: nexenta rollback problems. > Subject: Re: nexenta rollback problems. > > I have already look at it but I never find a way to reassign the previous > guid... Seems import_lu does the trick. Do you think that will work? sub nexenta_import_lu { my ($scfg, $zvol) = @_; nexenta_request($scfg, 'import_lu', 'scsidisk', "$scfg->{pool}/$zvol"); } sub volume_snapshot_rollback { my ($class, $scfg, $storeid, $volname, $snap) = @_; nexenta_delete_lu($scfg, $volname); nexenta_request($scfg, 'rollback', 'snapshot', "$scfg->{pool}/$volname\@$snap", ''); nexenta_import_lu($scfg, $volname); nexenta_add_lun_mapping_entry($scfg, $volname); } _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
