From: Martin Mailand <martin@tuxadero.com>
To: Gregory Farnum <gregory.farnum@dreamhost.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: osd crash during resync
Date: Tue, 24 Jan 2012 22:22:16 +0100 [thread overview]
Message-ID: <4F1F2108.10400@tuxadero.com> (raw)
In-Reply-To: <CAF3hT9CMxL6eQMgNebdMifZ9CgcVGHNPhqV30Auh+on9HBKefQ@mail.gmail.com>
Hi Greg,
ok, do you guys still need the core files, or could I delete them?
-martin
Am 24.01.2012 22:13, schrieb Gregory Farnum:
> On Tue, Jan 24, 2012 at 10:48 AM, Martin Mailand<martin@tuxadero.com> wrote:
>> Hi,
>> today I tried the btrfs patch mentioned on the btrfs ml. Therefore I
>> rebooted osd.0 with a new kernel and created a new btrfs on the osd.0, than
>> I took the osd.0 into the cluster. During the the resync of osd.0 osd.2 and
>> osd.3 crashed.
>> I am not sure, if the crashes happened because I played with osd.0, or if
>> they are bugs.
>
> These are OSD-level issues not caused by btrfs, so your new kernel
> definitely didn't do it. It's probably fallout from the backfill
> changes that got merged in last week. I created new bugs to track
> them: http://tracker.newdream.net/issues/1982 (1983, 1984). Sam and
> Josh are going wild on some other issues that we've turned up and
> these have been added to the queue as soon as somebody qualified can
> get to them. :)
> -Greg
> --
> 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
next prev parent reply other threads:[~2012-01-24 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 18:48 osd crash during resync Martin Mailand
2012-01-24 21:13 ` Gregory Farnum
2012-01-24 21:22 ` Martin Mailand [this message]
2012-01-24 21:25 ` Gregory Farnum
2012-01-25 22:08 ` Sage Weil
2012-01-26 10:18 ` Martin Mailand
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=4F1F2108.10400@tuxadero.com \
--to=martin@tuxadero.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gregory.farnum@dreamhost.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.