From: Stefan Priebe <s.priebe@profihost.ag>
To: Tommi Virtanen <tv@inktank.com>
Cc: Dan Mick <dan.mick@inktank.com>, Sam Just <sam.just@inktank.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: reproducable osd crash
Date: Tue, 26 Jun 2012 18:47:18 +0200 [thread overview]
Message-ID: <4FE9E796.4050000@profihost.ag> (raw)
In-Reply-To: <CADvuQRGS4xCyxbYVPNNPVyc4dZQVgnDXbHcTkKf0ZbscPCjewA@mail.gmail.com>
Am 26.06.2012 18:05, schrieb Tommi Virtanen:
> On Mon, Jun 25, 2012 at 10:48 PM, Stefan Priebe <s.priebe@profihost.ag> wrote:
>> Strange just copied /core.hostname and /usr/bin/ceph-osd no idea how this
>> can happen. For building I use the provided Debian scripts.
>
> Perhaps you upgraded the debs but did not restart the daemons? That
> would make the on-disk executable with that name not match the
> in-memory one.
No, i reboot after each upgrade ;-)
Right now i'm witing for a FS fix xfs or btrfs and i will then reproduce
the issue.
Stefan
next prev parent reply other threads:[~2012-06-26 16:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 12:55 reproducable osd crash Stefan Priebe - Profihost AG
2012-06-21 13:07 ` Stefan Priebe - Profihost AG
2012-06-21 13:13 ` Stefan Priebe - Profihost AG
2012-06-21 13:23 ` Stefan Priebe - Profihost AG
2012-06-21 19:57 ` Stefan Priebe
2012-06-22 16:01 ` Stefan Priebe - Profihost AG
2012-06-22 6:43 ` Stefan Priebe
2012-06-22 22:56 ` Dan Mick
2012-06-22 23:59 ` Sam Just
2012-06-23 6:32 ` Stefan Priebe
2012-06-25 16:39 ` Dan Mick
2012-06-25 17:19 ` Stefan Priebe
2012-06-25 21:01 ` Dan Mick
2012-06-25 21:18 ` Stefan Priebe
2012-06-26 0:11 ` Dan Mick
2012-06-26 5:15 ` Stefan Priebe
2012-06-26 5:48 ` Stefan Priebe
2012-06-26 16:05 ` Tommi Virtanen
2012-06-26 16:47 ` Stefan Priebe [this message]
2012-06-26 18:01 ` Sam Just
2012-06-27 7:22 ` Stefan Priebe - Profihost AG
2012-06-27 15:19 ` Sage Weil
2012-06-23 0:26 ` Dan Mick
2012-06-23 6:32 ` Stefan Priebe
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=4FE9E796.4050000@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=dan.mick@inktank.com \
--cc=sam.just@inktank.com \
--cc=tv@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.