All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@dreamhost.com>
To: madhusudhana <madhusudhana.u.acharya@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: timed out in osd1 error in dmes
Date: Tue, 13 Mar 2012 13:23:52 -0700	[thread overview]
Message-ID: <4F5FACD8.8090902@dreamhost.com> (raw)
In-Reply-To: <loom.20120313T083325-276@post.gmane.org>

On 03/13/2012 12:35 AM, madhusudhana wrote:
> Hi all,
> The server in which i have mounted file system using mount -t ceph
> is showing below errors in dmesg.
>
>
> libceph:  tid 79987 timed out on osd2, will reset osd
> libceph:  tid 81516 timed out on osd0, will reset osd
> libceph:  tid 81133 timed out on osd1, will reset osd
> libceph: skipping osd1 10.25.12.127:6800 seq 1 expected 2
> libceph:  tid 80108 timed out on osd2, will reset osd
> libceph:  tid 81134 timed out on osd1, will reset osd
> libceph:  tid 81641 timed out on osd1, will reset osd
>
>
> Is is because of this, write/copy operation in my cluster
> is slow ? is this a error which needs attention or can be
> safely ignored ?

These are usually harmless, and could just mean the osds can't keep up 
with the requests you're giving them. Given your other issues, it might 
be a symptom of a problem with your osds.

What filesystem are the osds using? Are there any warnings from these 
filesystems in dmesg?

>
> Thanks
> Madhusudhan


  reply	other threads:[~2012-03-13 20:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13  7:35 timed out in osd1 error in dmes madhusudhana
2012-03-13 20:23 ` Josh Durgin [this message]
2012-03-14  4:20   ` madhusudhana
2012-03-14 17:59     ` Sage Weil
2012-03-15  7:46       ` madhusudhana
2012-03-15 15:47         ` Sage Weil
2012-03-15 17:02           ` madhusudhana

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=4F5FACD8.8090902@dreamhost.com \
    --to=josh.durgin@dreamhost.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=madhusudhana.u.acharya@gmail.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 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.