> 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
oh, do you tried import_lu ? is it working ?
That's great :)
Damn, nexenta support is pretty poor...
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER"
Cc: pve-devel@pve.proxmox.com
Envoyé: Jeudi 20 Septembre 2012 07:10:31
Objet: RE: [pv
> 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 c
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/bo
> I'll tell the question to nexenta support.
I will commit the import_lu() code for testing now.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
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 s
>>Btw, do you have any idea how we can access snapshot data for backup
>>purposes?
2 ways :
1) clone the snapshot, assign a lun to it, backup it, remove the lun,remove the
clone
2) use "zfs send" through ssh. (and zfs receive to restore)
- Mail original -
De: "Dietmar Maurer"
> 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',
> 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/mail
> 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
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)
(
> 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
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"
> À: "Alexandre DERUMIER" , pve-
I have already look at it but I never find a way to reassign the previous
guid...
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER" , pve-devel@pve.proxmox.com
Envoyé: Mardi 18 Septembre 2012 17:39:03
Objet: nexenta rollback problems.
Nexenta rollback seems to only w
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
15 matches
Mail list logo
