CEPH filesystem development
 help / color / mirror / Atom feed
From: Stefan Kleijkers <stefan@unilogicnetworks.net>
To: Madhusudhana U <madhusudhana.u.acharya@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Partition for OSD journal
Date: Thu, 12 Apr 2012 20:12:59 +0200	[thread overview]
Message-ID: <4F871B2B.2060006@unilogicnetworks.net> (raw)
In-Reply-To: <loom.20120412T181758-343@post.gmane.org>

Hello,

Just partition the disk, like sda1, sda2, etc and add the following to 
your config:
[osd.0]
             osd journal = /dev/sda1

[osd.1]
             osd journal = /dev/sda2

etc...

So you can point the "osd journal" to a file or to a device.

The negative side to this is you have to partition the disk and have to 
add a different option for every osd. You could fix this with udev and 
make a logical naming scheme for the device like:
/dev/osd.0.journal
/dev/osd.1.journal
etc

That way you can add to your config:
[osd]
             osd journal = /dev/osd.$id.journal

Stefan

On 04/12/2012 06:22 PM, Madhusudhana U wrote:
> Hi all,
> I read in the wiki that, to have a better performance compared to file
> under OSD data dir, we can have a seperate partition for OSD journal.
> can someone suggest me, how i can mention this in ceph.conf file ?
> I have below lines in my ceph.conf file. Is this means I already have
> a partition for OSD journal
>
> [osd]
>          osd data = /data/osd.$id
>          keyring = /etc/ceph/keyring.$name
>          osd journal = /journal/osd.$id.journal
>
> /journal is a separate partition of 20G.
>
> Thanks
> __M
>
> --
> 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-04-12 18:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 16:22 Partition for OSD journal Madhusudhana U
2012-04-12 18:12 ` Stefan Kleijkers [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=4F871B2B.2060006@unilogicnetworks.net \
    --to=stefan@unilogicnetworks.net \
    --cc=ceph-devel@vger.kernel.org \
    --cc=madhusudhana.u.acharya@gmail.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