From: Stefan Priebe <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 after reboot
Date: Fri, 14 Dec 2012 20:47:08 +0100 [thread overview]
Message-ID: <50CB823C.90501@profihost.ag> (raw)
In-Reply-To: <alpine.DEB.2.00.1212141140590.22306@cobra.newdream.net>
Hi Sage,
this was just an idea and i need to fix MY uuid problem. But then the
crash is still a problem of ceph. Have you looked into my log?
Am 14.12.2012 20:42, schrieb Sage Weil:
> On Fri, 14 Dec 2012, Stefan Priebe wrote:
>> One more IMPORTANT note. This might happen due to the fact that a disk was
>> missing (disk failure) afte the reboot.
>>
>> fstab and mountpoint are working with UUIDs so they match but the journal
>> block device:
>> osd journal = /dev/sde1
>>
>> didn't match anymore - as the numbers got renumber due to the failed disk. Is
>> there a way to use some kind of UUIDs here too for journal?
>
> I think others have addressed the uuid question, but one note:
>
> The ceph-osd process has an internal uuid/fingerprint on the journal and
> data dir, and will refuse to start if they don't match.
Stefan
prev parent reply other threads:[~2012-12-14 19:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 8:12 osd crash after reboot Stefan Priebe
2012-12-14 8:22 ` Stefan Priebe
2012-12-14 9:14 ` Stefan Priebe
2012-12-14 14:52 ` Dennis Jacobfeuerborn
2012-12-14 15:01 ` Mark Nelson
2012-12-14 15:11 ` Stefan Priebe - Profihost AG
2012-12-14 15:20 ` Mark Nelson
2012-12-14 15:25 ` Stefan Priebe - Profihost AG
2012-12-14 16:06 ` Stefan Priebe - Profihost AG
2012-12-14 15:02 ` Stefan Priebe - Profihost AG
2012-12-14 19:42 ` Sage Weil
2012-12-14 19:47 ` Stefan Priebe [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=50CB823C.90501@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.