From: Fyodor Ustinov <ufm@ufm.su>
To: Gregory Farnum <gregf@hq.newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: OSD crash
Date: Sat, 28 May 2011 01:52:38 +0300 [thread overview]
Message-ID: <4DE02B36.2020007@ufm.su> (raw)
In-Reply-To: <BANLkTinQmX5HnzaxQE11Mst9Pjei7j90FA@mail.gmail.com>
On 05/27/2011 10:18 PM, Gregory Farnum wrote:
> Can you check out the recoverywq_fix branch and see if that prevents
> this issue? Or just apply the patch I've included below. :)
> -Greg
Looks as though this patch has helped.
At least this osd has completd rebalancing.
Great! Thanks!
WBR,
Fyodor.
next prev parent reply other threads:[~2011-05-27 22:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 0:12 OSD crash Fyodor Ustinov
2011-05-27 15:16 ` Gregory Farnum
2011-05-27 16:41 ` Fyodor Ustinov
2011-05-27 16:49 ` Gregory Farnum
2011-05-27 19:18 ` Gregory Farnum
2011-05-27 19:30 ` Fyodor Ustinov
2011-05-27 22:52 ` Fyodor Ustinov [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-07 16:42 osd crash Kaarlo Lahtela
[not found] <8566685.312.1362419807745.JavaMail.dspano@it1>
2013-03-04 18:02 ` OSD Crash Dave Spano
2012-08-22 20:31 OSD crash Andrey Korolyov
2012-08-22 22:33 ` Sage Weil
2012-08-22 22:55 ` Andrey Korolyov
2012-08-23 0:09 ` Gregory Farnum
2012-08-25 8:30 ` Andrey Korolyov
2012-08-26 16:52 ` Andrey Korolyov
2012-08-26 20:44 ` Sage Weil
2012-09-04 8:13 ` Andrey Korolyov
2012-09-04 15:32 ` Sage Weil
2012-06-16 12:57 Stefan Priebe
2012-06-16 13:34 ` Stefan Priebe
2012-06-17 21:16 ` Sage Weil
2012-06-18 6:41 ` Stefan Priebe - Profihost AG
2011-05-11 20:47 OSD Crash Mark Nigh
2011-05-11 21:06 ` Sage Weil
2011-05-11 21:39 ` Colin McCabe
2011-05-13 17:03 ` Mark Nigh
2011-05-13 18:34 ` Sage Weil
2011-05-11 13:12 Mark Nigh
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=4DE02B36.2020007@ufm.su \
--to=ufm@ufm.su \
--cc=ceph-devel@vger.kernel.org \
--cc=gregf@hq.newdream.net \
/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