From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: OSD crash
Date: Mon, 18 Jun 2012 08:41:28 +0200 [thread overview]
Message-ID: <4FDECD98.8010101@profihost.ag> (raw)
In-Reply-To: <Pine.LNX.4.64.1206171416150.20239@cobra.newdream.net>
Am 17.06.2012 23:16, schrieb Sage Weil:
> Hi Stefan,
>
> I opened http://tracker.newdream.net/issues/2599 to track this, but the
> dump strangely does not include the ceph version or commit sha1. What
> version were you running?
Sorry that was my build system it accidently removed the .git dir while
builing so the version string couldn't be compiled in.
It was 5efaa8d7799347dfae38333b1fd6e1a87dc76b28
Stefan
next prev parent reply other threads:[~2012-06-18 6:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 12:57 OSD crash 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 [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
2011-05-27 0:12 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
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=4FDECD98.8010101@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@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 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.