CEPH filesystem development
 help / color / mirror / Atom feed
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 dies / crahes directly after mkcephfs
Date: Fri, 15 Jun 2012 23:50:04 +0200	[thread overview]
Message-ID: <4FDBAE0C.6010606@profihost.ag> (raw)
In-Reply-To: <Pine.LNX.4.64.1206151445290.4551@cobra.newdream.net>

Am 15.06.2012 23:46, schrieb Sage Weil:
> On Fri, 15 Jun 2012, Stefan Priebe wrote:
>> Hi,
>>
>> i've seen several osd crashes on one of my machines directly after creating
>> the ceph fs.
>>
>> Attached is the osd log. I also have a core dump file. Do you need it?
>
> Also, are you mounting the ceph file system on the same node as the osd?
> This might be a sync(2)-induced deadlock.
No i use only rados / rbd and in this case i have never used the fs at 
all as it has happened directly after mkcephfs and -a start. So i didn't 
even had the chance.

> Putting a ceph fs mount on the same node as an osd is dicey in low memory
> situations.  On older glibcs and kernels without syncfs(2) support, it can
> easily deadlock.
Even this does not apply i have syncfs.

my send log shows: mount syncfs(2) syscall fully supported (by glibc and 
kernel)

Stefan

      reply	other threads:[~2012-06-15 21:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 21:22 osd dies / crahes directly after mkcephfs Stefan Priebe
2012-06-15 21:45 ` Sage Weil
2012-06-15 21:47   ` Stefan Priebe
2012-06-15 21:46 ` Sage Weil
2012-06-15 21:50   ` 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=4FDBAE0C.6010606@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox