All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amon Ott <a.ott@m-privacy.de>
To: Tommi Virtanen <tv@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: OSD deadlock with cephfs client and OSD on same machine
Date: Wed, 30 May 2012 08:59:26 +0200	[thread overview]
Message-ID: <201205300859.27181.a.ott@m-privacy.de> (raw)
In-Reply-To: <CADvuQRF5zC78hySCf3gYeJkRWGa+KjMKcY==0hqBxJrLhFv9dw@mail.gmail.com>

On Tuesday 29 May 2012 wrote Tommi Virtanen:
> On Tue, May 29, 2012 at 12:44 AM, Amon Ott <a.ott@m-privacy.de> wrote:
> > On Linux, if you run OSD on ext4 filesystem, have a cephfs kernel client
> > mount on the same system and no syncfs system call (as to be expected
> > with libc6 < 2.14 or kernel < 2.6.39), OSD deadlocks in sys_sync(). Only
> > reboot recovers the system.
>
> This is the classic issue of memory pressure needing free memory to be
> relieved. While syncfs(2) may make the hang less common, I do not
> think having syncfs(2) is enough; nothing sort of having a reserved
> memory pool guaranteed to be big enough to handle the request will,
> and maintaining that solution is hideously complex.

AFAIR, when the deadlocks came, there were some GB of the 12 GB RAM still 
unused, not even for caching. But it might be a problem with low memory, 
because we are running with 32 Bit.

Would it be possible to preallocate a significant amount of RAM for the 
purpose of syncing? I would not mind reserving a few 100 MB for that, but 
deadlocks must not happen in any case. Can the size of the journal give a 
hint on how much is needed?

Amon Ott
-- 
Dr. Amon Ott
m-privacy GmbH           Tel: +49 30 24342334
Am Köllnischen Park 1    Fax: +49 30 24342336
10179 Berlin             http://www.m-privacy.de

Amtsgericht Charlottenburg, HRB 84946

Geschäftsführer:
 Dipl.-Kfm. Holger Maczkowsky,
 Roman Maczkowsky

GnuPG-Key-ID: 0x2DD3A649
--
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

  reply	other threads:[~2012-05-30  6:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-29  7:44 OSD deadlock with cephfs client and OSD on same machine Amon Ott
2012-05-29 15:47 ` Sage Weil
2012-05-30  7:08   ` Amon Ott
2012-06-01  9:35     ` Amon Ott
2012-06-01 21:57       ` Tommi Virtanen
2012-11-05 20:17       ` Cláudio Martins
2012-11-06  7:54         ` Amon Ott
2012-05-29 16:18 ` Tommi Virtanen
2012-05-30  6:59   ` Amon Ott [this message]
2012-05-30 17:02     ` Tommi Virtanen

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=201205300859.27181.a.ott@m-privacy.de \
    --to=a.ott@m-privacy.de \
    --cc=ceph-devel@vger.kernel.org \
    --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.