From: Mark Nelson <mark.nelson@inktank.com>
To: Dennis Jacobfeuerborn <dennisml@conversis.de>
Cc: Stefan Priebe <s.priebe@profihost.ag>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: osd crash after reboot
Date: Fri, 14 Dec 2012 09:01:06 -0600 [thread overview]
Message-ID: <50CB3F32.2070106@inktank.com> (raw)
In-Reply-To: <50CB3D33.7070800@conversis.de>
On 12/14/2012 08:52 AM, Dennis Jacobfeuerborn wrote:
> On 12/14/2012 10:14 AM, 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?
>
> You should be able to use /dev/disk/by-uuid/* instead. That should give you
> a stable view of the filesystems.
I often map partitions to something in /dev/disk/by-partlabel and use
those in my ceph.conf files. that way disks can be remapped behind the
scenes and the ceph configuration doesn't have to change even if disks
get replaced.
>
> Regards,
> Dennis
>
> --
> 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-12-14 15:01 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 [this message]
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
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=50CB3F32.2070106@inktank.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dennisml@conversis.de \
--cc=s.priebe@profihost.ag \
/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.