From: Roberto Scudeller <beto.rvs@gmail.com>
To: xen-devel@lists.xensource.com
Subject: tapdisk2 dont remove in kernel 2.6.31.14
Date: Wed, 23 Mar 2011 15:02:57 -0300 [thread overview]
Message-ID: <AANLkTimBjRT9KTW9iosuJQWkEPEKv1QoFxbVu3Am33aD@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2408 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 2617 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2011-03-23 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 18:02 Roberto Scudeller [this message]
2011-03-24 0:16 ` tapdisk2 dont remove in kernel 2.6.31.14 Pasi Kärkkäinen
2011-03-24 1:53 ` Daniel Stodden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTimBjRT9KTW9iosuJQWkEPEKv1QoFxbVu3Am33aD@mail.gmail.com \
--to=beto.rvs@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).