[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] tapdisk2 dont remove in kernel 2.6.31.14


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Roberto Scudeller <beto.rvs@xxxxxxxxx>
  • Date: Wed, 23 Mar 2011 15:02:57 -0300
  • Delivery-date: Wed, 23 Mar 2011 11:08:49 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=mg5yBAUn4CxEr3DDyL/cjXLwo0krKbwne4242D7Jn4cOn2gff9WhNKnDTZanfqD0PR CmohaViAV3Kud3P56WkOAEF8+kVI+OyaNH1d9KbqNVoMR7mB8BzQZbfxPPUeeZuFFuvT eLz7WFMiveM4/VnSC9IZbmKRdRfRa8bVmHNDw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi all,

I try to use kernel 2.6.31.14 from the git with xen 4.0.2-rc3-pre.

I create tapdevice:
# tapdisk2 -n aio:/root/discoteste
/dev/xen/blktap-2/tapdev0

And I try remove this device:
# echo "1" > /sys/class/blktap2/blktap0/remove
And I cancel this:
^C-bash: echo: write error: Resource temporarily unavailable

In /var/log/messages:
Mar 23 14:09:23 tapdisk2[11178]: Created /dev/xen/blktap-2/control device
Mar 23 14:09:23 tapdisk2[11178]: Created /dev/xen/blktap-2/blktap0 device
Mar 23 14:09:23 tapdisk2[11178]: Created /dev/xen/blktap-2/tapdev0 device
Mar 23 14:09:23 tapdisk2[11178]: new interface: ring: 251, device: 253, minor: 0
Mar 23 14:09:23 tapdisk2[11178]: I/O queue driver: lio
Mar 23 14:09:23 kernel: [ 3900.429698] blktap_sysfs_create: adding attributes for dev ffff88006f57f400
Mar 23 14:09:23 kernel: [ 3900.429763] blktap_control_allocate_tap: allocated tap ffff88006a9f9800
Mar 23 14:09:23 tapdisk2[11178]: block-aio open('/root/discoteste')
Mar 23 14:09:23 tapdisk2[11178]: open(/root/discoteste) with O_DIRECT
Mar 23 14:09:23 tapdisk2[11178]: Image size:      pre sector_shift  [10736369664]     post sector_shift [20969472]
Mar 23 14:09:23 tapdisk2[11178]: opened image /root/discoteste (1 users, state: 0x00000001, type: 0)
Mar 23 14:09:23 tapdisk2[11178]: VBD CHAIN:
Mar 23 14:09:23 tapdisk2[11178]: /root/discoteste: 0
Mar 23 14:09:23 kernel: [ 3900.431130] blktap_ring_open: opening device blktap0
Mar 23 14:09:23 kernel: [ 3900.431137] blktap_ring_open: opened device 0
Mar 23 14:09:23 kernel: [ 3900.431227] blktap_ring_mmap: blktap: mapping pid is 11178
Mar 23 14:09:23 kernel: [ 3900.431267] blktap_validate_params: aio:/root/discoteste: capacity: 20969472, sector-size: 512
Mar 23 14:09:23 kernel: [ 3900.431294] blktap_validate_params: aio:/root/discoteste: capacity: 20969472, sector-size: 512
Mar 23 14:09:23 kernel: [ 3900.431316] blktap_device_create: minor 0 sectors 20969472 sector-size 512
Mar 23 14:09:23 kernel: [ 3900.431645] blktap_device_create: creation of 253:0: 0
Mar 23 14:09:56 kernel: [ 3931.416247] blktap_device_destroy: destroy device 0 users 0


When a DomU is destroy ( or shutdown), this tapdisk2 process keeps:
# ps -ef |grep tapdisk
root     11178     1 98 14:09 pts/0    00:47:44 tapdisk2 -n aio:/root/discoteste

When I kill the tapdisk2 process this device is removed.

Is there a patch for this?

Thanks for any help.

--
Roberto Scudeller


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.