Hi,
> My distro (openSuSE 12.1) has /usr/sbin/tapdisk for original tapdisk v1, and /usr/sbin/tapdisk2 for version 2 stuff. I'm replacing /usr/sbin/tapdisk2.
Mm, do you know where I could find the source for those tapdisk binaries ?
> This is attempting to just use "tap2:aio" for the image format ("tap2:tapdisk:aio" fails identically, as does "tap2:rbd:rbd/test"). In my /var/log/messages file, I see the following:
> Apr 23 10:34:51 se004922 kernel: [ 6328.409708] blktap_control_allocate_tap: allocated tap ffff8807a4898800
> Apr 23 10:34:51 se004922 tapdisk[32464]: tapdisk-control: init, 10 x 4k buffers
> Apr 23 10:34:51 se004922 tapdisk[32464]: I/O queue driver: lio
> Apr 23 10:34:51 se004922 tapdisk[32464]: tapdisk-log: started, level 0
> Apr 23 10:34:51 se004922 tapdisk[32464]: nbd: Set up local unix domain socket on path '/var/run/blktap-control/nbdclient32464'
> Apr 23 10:34:53 se004922 tapdisk[32464]: ERROR: errno -5 at tapdisk_control_read_message: failure reading message at offset 280/536
> Apr 23 10:34:53 se004922 tap-ctl: tap-err:tap_ctl_read_message: failure reading message
> Apr 23 10:34:53 se004922 tap-ctl: tap-err:tap_ctl_send_and_receive: failed to receive 'unknown' message
>
> That "nbd" portion is particularly puzzling - why would it try to start nbd when I've specified a simple tap2:aio image?
The tree I used seem to init some of the NBD logic in all cases (nbd
is integrated in the core rather than purely in the driver).
My guess is that the tree I used is close enough to the debian source
for it to work with just switching tapdisk, but different from
opensuse package.
Can you try to ./configure --prefix=/usr and then make install ?
This will replace all the binaries including tap-ctl. If they're in a
distinct package, you can pre-uninstall the blktap-utils from your
distro.
'
Cheers,
Sylvain
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
