<html><head></head><body>Maybe using dtrace or strace could give you ideas?<br><br><div class="gmail_quote">Alexandre DERUMIER <aderumier@odiso.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hi,<br /><br />the patch seem to generate now similar guid than nexenta<br /><br />600144f0a06f0700000055428993c0c1 34359738368 /dev/zvol/rdsk/MainPool/vm-296-disk-9 -> generate with last patch<br />600144f0a06f07000000558811e9da14 34359738368 /dev/zvol/rdsk/MainPool/vm-296-disk-8<br />600144f0a06f070000005c6f449515d5 34359738368 /dev/zvol/rdsk/MainPool/vm-296-disk-7<br />600144f0a26587000000519e535b0001 34359738368 /dev/zvol/rdsk/MainPool/vm-277-disk-1<br />600144f0a265870000005242d93c0001 34359738368 /dev/zvol/rdsk/MainPool/vm-291-disk-1-> generate with nexenta<br />600144f0a265870000005242dafb0003 34359738368 /dev/zvol/rdsk/MainPool/base-292-disk-1 -> generate with nexenta<br />600144f0a26587000000527922280001 34359738368 /dev/zvol/rdsk/MainPool/vm-296-disk-5<br />600144f675f1c980c38752a0647ba5e6 34359738368 /dev/zvol/rdsk/MainPool/vm-296-disk-6 -> generate with
previous patch<br />600144ff713ed897226e5d64732418ff 34359738368 /dev/zvol/rdsk/MainPool/vm-292-disk-3 -> generate with previous patch<br /><br />But It doesn't help for the gui error<br /><br />My understanding is that nexenta generate a cache somewhere, and something it's not filled<br /><br />some log:<br /><br />Nov 06 17:03:09 (1:1.5) EXCEPTION: ObjectNotFound: ScsiDiskContainer::list_lun_mapping_entries(MainPool/vm-296-disk-7): Unable to locate the specified zvol 'MainPool/vm-296-disk-7' <br /><br />2013-11-06 17:10:08,255 nza ERROR com.nexenta.nms::/Root/Stmf/ScsiDisk::list_lun_mapping_entries(dbus.String(u'MainPool/vm-296-disk-9')): com.nexenta.nms.ObjectNotFound: Unable to locate the specified zvol 'MainPool/vm-296-disk-9' <br /><br /><br /><br />after waiting some minutes, or rlauching the nms service (webgui service) (#svcadm restart nms)<br /><br />It's working again<br /><br />(The module is in python, but closed sources, compiled .pyc, I can't see what it
is doing)<br /><br /><br />restarting nms stop the web gui for some minutes,<br /><br />but in the logs it's showing:<br />Nov 06 17:28:15 Starting...<br />Nov 06 17:28:15 Syncing devices...<br />Nov 06 17:28:22 Syncing LUNs...<br /><br />So I think it's rebuild the luns cache or something similar<br /><br /><br />I'll try to find an easy way to reload this cache. (through ssh command)<br /><br /><br />----- Mail original -----<br /><br />De: "Michael Rasmussen" <mir@datanom.net> <br />À: "Alexandre DERUMIER" <aderumier@odiso.com>, pve-devel@pve.proxmox.com <br />Envoyé: Mardi 5 Novembre 2013 19:28:52 <br />Objet: Re: [pve-devel] ZFS plugin: Patch to solve issue with nexenta <br /><br />On Tue, 05 Nov 2013 18:45:34 +0100 (CET) <br />Alexandre DERUMIER <aderumier@odiso.com> wrote: <br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">I'll try tomorrow ! </blockquote><br />If the solution
works it will cause no problems to only use 11 digits <br />when naming a lun since max luns per target is limited to 2^14 or 16384 <br />and using 11 hex digits is an astronomic large number 11^16 <br /></pre></blockquote></div><br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.</body></html>