Re: [pve-devel] nexenta rollback problems.
response from nexenta:
Hello,
Your case # 00014435: commstar : keep the disk guid after unmap/remap a lun
(sa-api) has been updated as follows:
Alexandre,
There is no way to do this via SA-API .
The only way to do it is via bash you as mentioned .
#stmfadm create-lu -p guid=* LUN GUID* /dev/rdsk/...
Please test it out if it works for your use.
Best regards, Abhishek
Nexenta Support Center
http://nexenta.com/corp/support
- Mail original -
De: Alexandre DERUMIER aderum...@odiso.com
À: Dietmar Maurer diet...@proxmox.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Mercredi 19 Septembre 2012 08:34:00
Objet: Re: [pve-devel] nexenta rollback problems.
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
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] nexenta rollback problems.
Your case # 00014435: commstar : keep the disk guid after unmap/remap a lun (sa-api) has been updated as follows: Alexandre, There is no way to do this via SA-API . The only way to do it is via bash you as mentioned . Our current code use delete_lu/import_lu, and that does not change the GUID here. - Dietmar ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] nexenta rollback problems.
oh, do you tried import_lu ? is it working ? I works for me, so I already committed that code. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] nexenta rollback problems.
I guess that cause serious trouble when used with open-iscsis/dm-multipath. You already observer problems with that? s/observer/observed/ ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] nexenta rollback problems.
Yes, indeed. that's really a pain. (BTW, I don't use multipath anymore, only lacp, take too much cpu with a lot of luns). The only way is to dynamicaly build the path, finding the good /dev/by-id, when the guest is starting.(find the lunid with nexentaapi, then search the multipath device) (That's why I have asked you so some months ago to put the activate storage before the qemu command line build) - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com Envoyé: Mardi 18 Septembre 2012 18:30:50 Objet: RE: nexenta rollback problems. I guess that cause serious trouble when used with open-iscsis/dm-multipath. You already observer problems with that? I have already look at it but I never find a way to reassign the previous guid... - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Alexandre DERUMIER aderum...@odiso.com, pve- de...@pve.proxmox.com Envoyé: Mardi 18 Septembre 2012 17:39:03 Objet: nexenta rollback problems. Nexenta rollback seems to only work with delete_lu/create_lu. But this changes the GUID of the volume. Any idea how to avoid that? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] nexenta rollback problems.
Yes, indeed. that's really a pain. (BTW, I don't use multipath anymore, only lacp, take too much cpu with a lot of luns). I really tried hard, but my final conclusion is that open-iscsi/dm-multipath does not work well with dynamically allocated luns (like we do in the nexenta plugin). I know, you came to that conclusion months ago. So I will give up now, and we simply use libiscsi for the nexenta plugin for now. Maybe future versions of libiscsi will support some kind of multipath - until that happens one can use lcap as workaround. - Dietmar ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] nexenta rollback problems.
So I will give up now, and we simply use libiscsi for the nexenta plugin for now. Btw, do you have any idea how we can access snapshot data for backup purposes? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
