From: Zenon Panoussis <oracle@provocation.net>
To: ceph-devel@vger.kernel.org
Subject: Re: kernel errors, timeouts and qemu-img usage
Date: Tue, 03 May 2011 18:14:28 +0200 [thread overview]
Message-ID: <4DC029E4.3@provocation.net> (raw)
In-Reply-To: <4DBFEC14.1040102@science-computing.de>
On 05/03/2011 01:50 PM, Christoph Raible wrote:
> First I alwas get on ceph -w following "error":
> "[WRN] message from mon2 was stamped 12.271440s in the future clocks not synchronized"
> But i have synchronized my clocks 1 min befor with the same ntp-server..
But are they really in sync?
> The second error is, that I can't create / start an qemu-image on the ceph-filesystem.
> I want to start a kvm virtual machine with the virt-manager.
> I create an image with
> "qemu-img create -f qcow2 Platte-qcow2.img 10G"
> The virtual machine never starts. It hangs on look for the "harddisk"
The image file has to appear as a block device; I suspect you need
http://ceph.newdream.net/wiki/QEMU-RBD .
I have no clue about the third error; what were you doing when you got it?
The fourth error is a timeout too. The file you are trying to write is 2.4
GiB in size (dd defaults to 512 bytes, so 512*5000000 bytes). Your journal
is only 500 MB and you are replicating the data and you are logging 20 on
the same physical hard drive, so I suspect very serious I/O saturation.
Try bs= together with count= for better dd control and write a much smaller
file. Try disabling hung_task_timeout as the error message suggested. Try
also nice and ionice on dd. The problem might be something unrelated, but
this is a quick way to start figuring what's happening.
Z
next prev parent reply other threads:[~2011-05-03 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 11:50 kernel errors, timeouts and qemu-img usage Christoph Raible
2011-05-03 16:14 ` Zenon Panoussis [this message]
2011-05-03 16:43 ` Tommi Virtanen
2011-05-04 9:33 ` Christoph Raible
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=4DC029E4.3@provocation.net \
--to=oracle@provocation.net \
--cc=ceph-devel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.