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
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
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
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
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)
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,
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
