From: Denis Fondras <ceph@ledeuns.net>
To: Gregory Farnum <greg@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Is Ceph recovery able to handle massive crash
Date: Wed, 09 Jan 2013 09:30:53 +0100 [thread overview]
Message-ID: <50ED2ABD.4050003@ledeuns.net> (raw)
In-Reply-To: <CAPYLRziWs+mpHCB=FXin2UYA-wwrqiqPe1B--_kVN_+ex0apkQ@mail.gmail.com>
Hello,
Le 09/01/2013 00:36, Gregory Farnum a écrit :
>
> It looks like it's taking approximately forever for writes to complete
> to disk; it's shutting down because threads are going off to write and
> not coming back. If you set "osd op thread timeout = 60" (or 120) it
> might manage to churn through, but I'd look into why the writes are
> taking so long — bad disk, fragmented btrfs filesystem, or something
> else.
I believe it is a BTRFS issue as when I mkfs.btrfs the volume and rejoin
it to the cluster, it works (OSD is staying up).
Denis
--
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
prev parent reply other threads:[~2013-01-09 8:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 12:19 Is Ceph recovery able to handle massive crash Denis Fondras
2013-01-05 15:24 ` Gregory Farnum
2013-01-07 17:25 ` Denis Fondras
2013-01-07 21:30 ` Gregory Farnum
2013-01-08 8:44 ` Denis Fondras
2013-01-08 12:57 ` Denis Fondras
2013-01-08 13:10 ` Wido den Hollander
2013-01-08 13:36 ` Wido den Hollander
2013-01-08 13:51 ` Moore, Shawn M
2013-01-08 14:53 ` Denis Fondras
2013-01-08 17:09 ` Gregory Farnum
2013-01-08 19:44 ` Denis Fondras
2013-01-08 23:36 ` Gregory Farnum
2013-01-09 8:30 ` Denis Fondras [this message]
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=50ED2ABD.4050003@ledeuns.net \
--to=ceph@ledeuns.net \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox