From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roberto Scudeller Subject: tapdisk2 dont remove in kernel 2.6.31.14 Date: Wed, 23 Mar 2011 15:02:57 -0300 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0485156524==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0485156524== Content-Type: multipart/alternative; boundary=0016e6dd966bb57e15049f2a2ba5 --0016e6dd966bb57e15049f2a2ba5 Content-Type: text/plain; charset=ISO-8859-1 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 --0016e6dd966bb57e15049f2a2ba5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all,

I try to use kernel 2.6.31.14 from the git with xen 4.0.2-rc= 3-pre.

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

And I try remove this device:
# echo &= quot;1" > /sys/class/blktap2/blktap0/remove
And I cancel this:
^C-bash: echo: write error: Resource temporarily unav= ailable

In /var/log/messages:
Mar 23 14:09:23 tapdisk2[11178]: Cr= eated /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 <= br>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 attribut= es for dev ffff88006f57f400
Mar 23 14:09:23 kernel: [ 3900.429763] blkta= p_control_allocate_tap: allocated tap ffff88006a9f9800
Mar 23 14:09:23 t= apdisk2[11178]: block-aio open('/root/discoteste')
Mar 23 14:09:23 tapdisk2[11178]: open(/root/discoteste) with O_DIRECT
M= ar 23 14:09:23 tapdisk2[11178]: Image size:=A0 =A0=A0=A0 pre sector_shift= =A0 [10736369664] =A0=A0=A0 post sector_shift [20969472]
Mar 23 14:09:2= 3 tapdisk2[11178]: opened image /root/discoteste (1 users, state: 0x0000000= 1, type: 0)
Mar 23 14:09:23 tapdisk2[11178]: VBD CHAIN:
Mar 23 14:09:23 tapdisk2[11= 178]: /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 pi= d is 11178
Mar 23 14:09:23 kernel: [ 3900.431267] blktap_validate_params= : aio:/root/discoteste: capacity: 20969472, sector-size: 512
Mar 23 14:0= 9:23 kernel: [ 3900.431294] blktap_validate_params: aio:/root/discoteste: c= apacity: 20969472, sector-size: 512
Mar 23 14:09:23 kernel: [ 3900.431316] blktap_device_create: minor 0 sector= s 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.4162= 47] blktap_device_destroy: destroy device 0 users 0


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

When I kil= l the tapdisk2 process this device is removed.

Is there a patch for this?

Thanks for any help.

--
Ro= berto Scudeller


--0016e6dd966bb57e15049f2a2ba5-- --===============0485156524== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0485156524==--