It sounds like maybe you're using Xen? The rbd writeback window option only
works for userspace rbd implementations (eg, KVM).
If you are using KVM, you probably want 8192 (~80MB) rather than 8192000
(~8MB).
What options are you running dd with? If you run a rados bench from both
On Monday, March 19, 2012 at 7:33 AM, ruslan usifov wrote:
Hello
I have follow stack trace:
#0 0xb77fa424 in __kernel_vsyscall ()
(gdb) bt
#0 0xb77fa424 in __kernel_vsyscall ()
#1 0xb77e98a0 in raise () from /lib/i386-linux-gnu/
libpthread.so.0
#2 0x08230f8b in ?? ()
#3 signal
Nope, I`m using KVM for rbd guests. Surely I`ve been noticed that Sage
mentioned too small value and I`ve changed it to 64M before posting
previous message with no success - both 8M and this value cause a
performance drop. When I tried to wrote small amount of data that can
be compared to
On 03/19/2012 11:13 AM, Andrey Korolyov wrote:
Nope, I`m using KVM for rbd guests. Surely I`ve been noticed that Sage
mentioned too small value and I`ve changed it to 64M before posting
previous message with no success - both 8M and this value cause a
performance drop. When I tried to wrote
2012/3/19 Greg Farnum gregory.far...@dreamhost.com:
On Monday, March 19, 2012 at 7:33 AM, ruslan usifov wrote:
Hello
I have follow stack trace:
#0 0xb77fa424 in __kernel_vsyscall ()
(gdb) bt
#0 0xb77fa424 in __kernel_vsyscall ()
#1 0xb77e98a0 in raise () from /lib/i386-linux-gnu/
So, we've been talking about an in-memory buffer that would contain
debug-level messages, and a separate thread/process [1] that would
write a subset of these to disk. Thus, on crash, we'd have a lot of
detail available (the ring buffer entries not yet overwritten),
without paying the
On Monday, March 19, 2012 at 11:44 AM, ruslan usifov wrote:
Sorry but no, i use precompiled binaries from this
http://ceph.newdream.net/debian. Perhaps this helps, initialy i
configure all ceph services mon, mds, osd, but then i test only rdb
and remove all mds from cluster (3 vmware machines)
