CEPH filesystem development
 help / color / mirror / Atom feed
From: Nathan Cutler <ncutler@suse.cz>
To: Jai <jai_97@rediffmail.com>
Cc: dang@redhat.com, Loic Dachary <loic@dachary.org>,
	ceph-devel@vger.kernel.org
Subject: Re: make error while building ceph
Date: Tue, 1 Mar 2016 21:15:45 +0100	[thread overview]
Message-ID: <56D5F871.2040901@suse.cz> (raw)
In-Reply-To: <CAPpuMWzZHMLSTRuWcvwbQLQ9hSj2+BufYLB5BTAys+0_KDHh4g@mail.gmail.com>

On 03/01/2016 03:39 PM, Jai wrote:
> I saw one report of a RAM issue.
> I have 2G on the VM - and  it was hung for > half a day.

I've found that compiling Ceph requires at least 8GB of RAM - anything 
less is a recipe for failure. I have not tried using cmake, though.

-- 
Nathan Cutler
Software Engineer Distributed Storage
SUSE LINUX, s.r.o.
Tel.: +420 284 084 037

  reply	other threads:[~2016-03-01 20:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-28 10:29 make error while building ceph Jai
2016-02-28 10:48 ` Loic Dachary
2016-02-28 10:55   ` Jai
2016-02-28 11:09     ` Loic Dachary
2016-02-29 14:34       ` Jai
2016-02-29 15:15         ` Loic Dachary
2016-02-29 17:13           ` Jai
2016-02-29 17:34             ` Loic Dachary
2016-03-01 13:45             ` Daniel Gryniewicz
2016-03-01 14:39               ` Jai
2016-03-01 20:15                 ` Nathan Cutler [this message]
2016-03-02  2:59                   ` Jai
2016-03-02  4:07                     ` David Zafman
2016-03-02  4:19                       ` Robert LeBlanc
2016-03-02  6:40                         ` Jai
2016-03-04  9:58                           ` Jai
2016-03-04 10:53                             ` John Spray
2016-03-04 18:44                               ` Jai
2016-03-09  9:17                                 ` Jai
2016-03-30 20:59                                   ` Noah Watkins
2016-03-30 22:18                                     ` Josh Durgin

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=56D5F871.2040901@suse.cz \
    --to=ncutler@suse.cz \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dang@redhat.com \
    --cc=jai_97@rediffmail.com \
    --cc=loic@dachary.org \
    /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