From: Frederik Thuysbaert <frederik.thuysbaert@gmail.com>
To: Sylvain Munaut <s.munaut@whatever-company.com>
Cc: "James Harper" <james.harper@bendigoit.com.au>,
"Pasi Kärkkäinen" <pasik@iki.fi>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-devel] Xen blktap driver for Ceph RBD : Anybody wants to test ? :p
Date: Tue, 13 Aug 2013 16:59:55 +0200 [thread overview]
Message-ID: <520A49EB.9090301@gmail.com> (raw)
In-Reply-To: <CAF6-1L6jJvYuHN+BoucU2RNzv2R9dpMhbD1UVF96mBPO25FM5g@mail.gmail.com>
Hi,
I have been testing this a while now, and just finished testing your
untested patch. The rbd caching problem still persists.
The system I am testing on has the following characteristics:
Dom0:
- Linux xen-001 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64
- Most recent git checkout of blktap rbd branch
DomU:
- Same kernel as dom0
- Root (xvda1) is a logical volume on dom0
- xvda2 is a Rados Block Device format 1
Let me start by saying that the errors only occur with RBD client
caching ON.
I will give the error messages of both dom0 and domU before and after I
applied the patch.
Actions in domU to trigger errors:
~# mkfs.xfs -f /dev/xvda2
~# mount /dev/xvda2 /mnt
~# bonnie -u 0 -g 0 /mnt
Error messages:
BEFORE patch:
Without RBD cache:
dom0: no errors
domU: no errors
With RBD cache:
dom0: no errors
domU:
Aug 13 18:18:33 debian-vm-101 kernel: [ 37.960475] lost page write due
to I/O error on xvda2
Aug 13 18:18:33 debian-vm-101 kernel: [ 37.960488] lost page write due
to I/O error on xvda2
Aug 13 18:18:33 debian-vm-101 kernel: [ 37.960501] lost page write due
to I/O error on xvda2
...
Aug 13 18:18:52 debian-vm-101 kernel: [ 56.394645] XFS (xvda2):
xfs_do_force_shutdown(0x2) called from line 1007 of file
/build/linux-s5x2oE/linux-3.2.46/fs/xfs/xfs_log.c. Return address =
0xffffffffa013ced5
Aug 13 18:19:19 debian-vm-101 kernel: [ 83.941539] XFS (xvda2):
xfs_log_force: error 5 returned.
Aug 13 18:19:19 debian-vm-101 kernel: [ 83.941565] XFS (xvda2):
xfs_log_force: error 5 returned.
...
AFTER patch:
Without RBD cache:
dom0: no errors
domU: no errors
With RBD cache:
dom0:
Aug 13 16:40:49 xen-001 kernel: [ 94.954734] tapdisk[3075]: segfault
at 7f749ee86da0 ip 00007f749d060776 sp 00007f748ea7a460 error 7 in
libpthread-2.13.so[7f749d059000+17000]
domU:
Same as before patch.
I would like to add that I have the time to test this, we are happy to
help you in any way possible. However, since I am no C developer, I
won't be able to do much more than testing.
Regards
Frederik
On 13-08-13 11:20, Sylvain Munaut wrote:
> Hi,
>
>> I hope not. How could I tell? It's not something I've explicitly enabled.
> It's disabled by default.
>
> So you'd have to have enabled it either in ceph.conf or directly in
> the device path in the xen config. (option is 'rbd cache',
> http://ceph.com/docs/next/rbd/rbd-config-ref/ )
>
> Cheers,
>
> Sylvain
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-08-13 14:59 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 15:05 Xen blktap driver for Ceph RBD : Anybody wants to test ? :p Sylvain Munaut
2013-04-18 19:35 ` Wido den Hollander
2013-04-19 14:37 ` Sylvain Munaut
2013-04-19 14:40 ` Bernard Grymonpon
2013-04-23 10:02 ` Sylvain Munaut
2013-04-23 14:56 ` Bernard Grymonpon
2013-04-23 15:06 ` Sylvain Munaut
2013-04-23 19:13 ` Bernard Grymonpon
2013-04-23 16:38 ` Nick Couchman
2013-04-23 18:51 ` Sylvain Munaut
2013-04-23 20:09 ` Nick Couchman
2013-04-26 13:07 ` Sylvain Munaut
2013-04-26 15:51 ` Sage Weil
2013-04-26 17:10 ` Sylvain Munaut
2013-04-19 6:45 ` Pasi Kärkkäinen
2013-04-19 14:41 ` [Xen-devel] " Sylvain Munaut
2013-11-29 11:05 ` James Harper
2013-11-29 15:11 ` Sylvain Munaut
2013-12-01 4:08 ` James Harper
2013-12-03 15:46 ` Sylvain Munaut
2013-08-01 2:12 ` James Harper
2013-08-05 9:41 ` [Xen-devel] " Sylvain Munaut
2013-08-05 9:45 ` James Harper
2013-08-05 11:01 ` Sylvain Munaut
2013-08-05 11:03 ` James Harper
2013-08-05 11:12 ` Pasi Kärkkäinen
2013-08-05 12:03 ` [Xen-devel] " Sylvain Munaut
2013-08-05 13:35 ` George Dunlap
2013-08-05 13:55 ` Sylvain Munaut
2013-08-05 14:04 ` George Dunlap
2013-08-05 15:18 ` Wei Liu
2013-08-05 15:20 ` George Dunlap
2013-08-05 15:32 ` Wei Liu
2013-08-09 0:12 ` James Harper
2013-08-09 9:21 ` Sylvain Munaut
2013-08-11 0:51 ` James Harper
2013-08-11 1:02 ` James Harper
2013-08-12 14:13 ` Sylvain Munaut
2013-08-12 23:26 ` James Harper
2013-08-13 0:39 ` James Harper
2013-08-13 8:32 ` Sylvain Munaut
2013-08-13 9:12 ` James Harper
2013-08-13 9:20 ` Sylvain Munaut
2013-08-13 14:59 ` Frederik Thuysbaert [this message]
[not found] ` <520A4945.1030907@gmail.com>
2013-08-13 15:39 ` Sylvain Munaut
2013-08-13 23:39 ` James Harper
2013-08-13 23:43 ` Sylvain Munaut
2013-08-13 23:51 ` James Harper
2013-08-13 23:59 ` James Harper
2013-08-14 13:13 ` Sylvain Munaut
2013-08-14 13:16 ` James Harper
2013-08-15 7:20 ` James Harper
2013-08-16 1:02 ` James Harper
2013-08-14 8:43 ` Frederik Thuysbaert
2013-08-14 15:03 ` Sylvain Munaut
2013-08-16 8:27 ` Frederik Thuysbaert
2013-08-14 8:47 ` Frederik Thuysbaert
2013-08-13 21:47 ` James Harper
-- strict thread matches above, loose matches on Subject: below --
2013-06-21 7:21 Nathan O'Sullivan
2013-06-21 11:21 ` Sylvain Munaut
2013-07-01 9:57 ` Sylvain Munaut
2013-07-02 3:32 ` Nathan O'Sullivan
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=520A49EB.9090301@gmail.com \
--to=frederik.thuysbaert@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=james.harper@bendigoit.com.au \
--cc=pasik@iki.fi \
--cc=s.munaut@whatever-company.com \
--cc=xen-devel@lists.xen.org \
/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