From: Owen Synge <osynge@suse.com>
To: yue longguang <yuelongguang@gmail.com>, ceph-devel@vger.kernel.org
Subject: Re: questions about erasure coded pool and rados
Date: Fri, 17 Oct 2014 12:16:13 +0200 [thread overview]
Message-ID: <5440EC6D.9060501@suse.com> (raw)
In-Reply-To: <CAPaK2r_B8TjUo63P3d-XOOQzdvz_bUhpgPHw9TXLngms4=4c9Q@mail.gmail.com>
An erasure encoded pool cannot be accessed directly using rbd. For this
reason we need a cache pool and an erasure pool. This not only allows
supporting rbd but increases performance.
http://karan-mj.blogspot.de/2014/04/erasure-coding-in-ceph.html
http://docs.ceph.com/docs/master/rados/operations/pools/
http://ceph.com/docs/master/rados/operations/cache-tiering/
Good luck
Owen
On 10/17/2014 12:13 PM, yue longguang wrote:
> 1. why erasure coded pool does not work with rbd?
> 2. i used rados command to put a file into erasue coded pool,then rm
> it. why the file remains on osd's backend fs all the time?
> 3. what is the best use case with erasure coded pool?
>
> 4. command of 'rados ls' is to list objects, where are the object-name stored?
> 5.when a rbd file is put on erasure coded pool, where is the
> infomation(rbd name) of the rbd stored?
>
> thanks
> --
> 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
>
next prev parent reply other threads:[~2014-10-17 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 10:13 questions about erasure coded pool and rados yue longguang
2014-10-17 10:16 ` Owen Synge [this message]
2014-10-17 13:10 ` Loic Dachary
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=5440EC6D.9060501@suse.com \
--to=osynge@suse.com \
--cc=ceph-devel@vger.kernel.org \
--cc=yuelongguang@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 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.