<div dir="ltr"><div class="gmail_default" style="font-family:courier new,monospace"><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Sep 30, 2013 at 4:19 AM, Ritesh Nanda <span dir="ltr"><<a href="mailto:riteshnanda09@gmail.com" target="_blank">riteshnanda09@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div>Hello ,<br><br></div>I have grizzly setup , in which i run cinder using IBM storvize 3700.<br>
</div>Cinder shows a weird behavior every time i create a volume of some size and attach it to a vm , it shows some different size .<br>
<br></div>e.g i create a 4gb volume and attach it to a vm it shows of 15gb , this is every-time different sometimes it shows a volume smaller of the size it created.<br><br></div>While attaching a volume to a vm sometimes i get error on compute-nodes stating <br>
<br><br>d9f36a440abdf2fdd] [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] <b>Failed to attach volume 676ef5b1-129b-4d42-b38d-df2005a3d634 at /dev/vdc</b><br>2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] Traceback (most recent call last):<br>
2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2878, in _attach_volume<br>2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] mountpoint)<br>
2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 981, in attach_volume<br>2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] disk_dev)<br>
2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__<br>2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] self.gen.next()<br>
2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 968, in attach_volume<br>2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] virt_dom.attachDeviceFlags(conf.to_xml(), flags)<br>
2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 187, in doit<br>2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] result = proxy_call(self._autowrap, f, *args, **kwargs)<br>
2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 147, in proxy_call<br>2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] rv = execute(f,*args,**kwargs)<br>
2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 76, in tworker<br>2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] rv = meth(*args,**kwargs)<br>
2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] File "/usr/lib/python2.7/dist-packages/libvirt.py", line 422, in attachDeviceFlags<br>2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] if ret == -1: raise libvirtError ('virDomainAttachDeviceFlags() failed', dom=self)<br>
2013-09-30 15:17:46.562 31953 TRACE nova.compute.manager [instance: b9f128a9-d3e3-42a1-9511-74868b625b1b] <b>libvirtError: internal error unable to execute QEMU command 'device_add': Duplicate ID 'virtio-disk2' for device</b><br>
<br></div>Then if i change the mount point from /dev/vdc to something random mount point , it attaches the disk. But still showing different sizes problem remains.<br><br></div>Restarting open-iscsi services and reattaching the volume to the vm solves the issue.<br>
<br></div><div>Attaching my cinder.conf<br><br><br></div>Has anyone encountered this problem , or any help would be really appreciated.<span class="HOEnZb"><font color="#888888"><br><br><br><br><div><div><div><br clear="all">
<div><div><div><div><div><br>-- <br><p style="margin:0cm 0cm 0pt;color:rgb(0,0,153)">
<b><span style="font-size:10pt;font-family:Arial"> With Regards <br></span></b></p><p style="margin:0cm 0cm 0pt;color:rgb(0,0,153)"><b><span style="font-size:10pt;font-family:Arial"> Ritesh Nanda<br></span></b></p><p style="margin:0cm 0cm 0pt;color:rgb(0,0,153)">
</p><p style="margin:0cm 0cm 0pt;color:rgb(51,51,51)"><span style="color:rgb(0,0,153)"></span><span style="font-size:9pt;color:rgb(51,51,51);font-family:Arial"><span style="color:rgb(51,51,255)"><b><span style="color:rgb(0,0,153)"></span></b></span></span><span style="font-size:9pt;color:rgb(51,51,51);font-family:Arial"><span style="color:rgb(51,51,255)"><b><span style="color:rgb(0,0,153)"><br>
</span></b></span></span></p><a href="http://www.ericsson.com/" target="_blank"></a><p style="margin:0cm 0cm 0pt"><span style="font-size:9pt;font-family:Arial"><br><br></span></p>
</div></div></div></div></div></div></div></div></font></span></div>
<br>_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br></blockquote></div><div class="gmail_default" style="font-family:'courier new',monospace">Hi Ritesh,</div><div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace">
Not positive on the trace you've shown, but it seems like you in fact already have a device attached at that mount point (could try just using "auto", and see how things go that way).</div><div class="gmail_default" style="font-family:'courier new',monospace">
<br></div><div class="gmail_default" style="font-family:'courier new',monospace">As far as your observation about the volume being a "different" size, what are you using to determine this? I'd first ask what "cinder list or show" says the volume is in comparison to what you created, as well as possible what the IBM device says it's created. If you're talking about something specific after attach looking "different" than what you expected, I suspect you've got multiple attaches going on which may explain the confusion with the mount-points as well.</div>
<div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace">Thanks,</div><div class="gmail_default" style="font-family:'courier new',monospace">
John</div><br></div></div>