All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Disabling journal
Date: Mon, 12 Nov 2012 15:48:32 +0100	[thread overview]
Message-ID: <50A10C40.9090909@profihost.ag> (raw)
In-Reply-To: <alpine.DEB.2.00.1211120639540.28418@cobra.newdream.net>

Am 12.11.2012 15:42, schrieb Sage Weil:
> On Sun, 11 Nov 2012, Stefan Priebe wrote:
>> Hi Sage,
>>
>>> With btrfs, yes, although this isn't something we have tested in a while.
>> I'm not using btrfs as long as the devs claim it is not ready for prod.
>
> In that case, the journal is needed for consistency of the fs; we rely on
> writeahead journaling.  It can't be turned off.
>
> Putting it on a ramdisk in this case is interesting for performance, but
> it means that a crash/reboot/powerloss event leaves the fs in an
> inconsistent and unusable state.

But only if for replicas 2 both nodes crash / have a powerloss?

> The only time tmpfs is potentially useful in production is when you're
> using btrfs *and* have independent backup power sources for replicas (and
> can thus avoid worrying about a site-wide power failure and loss of
> journal).  (Or have relaxed requirements for the durability of recent
> writes.)
What happens for XFS and replicas two and ONE host has a power loss? The 
other replica / journal should be still there.

I've no idea where to put the journal on.

I mean i've 8 SSDs per Host one per osd each with a write IOP/s speed of 
45.000 iops to whole IOP/s write speed of 360.000 IOP/s per Node.

Which journal device can handle this? And if i put the journal on the 
same disk as the OSD it has to copy the data around.

Greets,
Stefan

  reply	other threads:[~2012-11-12 14:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-11 14:29 Disabling journal Stefan Priebe - Profihost AG
2012-11-11 15:24 ` Sage Weil
2012-11-11 21:33   ` Stefan Priebe
2012-11-12 14:42     ` Sage Weil
2012-11-12 14:48       ` Stefan Priebe - Profihost AG [this message]
2012-11-12 14:59         ` Sage Weil

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=50A10C40.9090909@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.