From: Raghunandhan <raghunandhan.g@iihtcloudsolutions.com>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: [ceph-commit] Ceph Zfs
Date: Fri, 26 Oct 2012 12:02:23 +0630 [thread overview]
Message-ID: <1e5cd344bedc185dd0cf7a930790bc6a@iihtcloudsolutions.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1210250834010.25762@cobra.newdream.net>
Also the open bug which is pending i have tried with it. Ceph-osd
starts up with zfs volume after the ceph service is up in sometime the
osd's stop working. I have been working around with releases from
ceph-0.30 till the latest 0.54 to check with zfs compatibility.
Kindly let me know if this can happen in any way it would become a
breakthrough in our storage design until btrfs becomes stable.
---
Regards,
Raghunandhan.G
IIHT Cloud Solutions Pvt. Ltd.
#15, 4th Floor, 'A' Wing, Sri Lakshmi Complex,
St. Marks Road, Bangalore - 560 001, India
On 25-10-2012 22:06, Sage Weil wrote:
> [moved to ceph-devel]
>
> On Thu, 25 Oct 2012, Raghunandhan wrote:
>> Hi All,
>>
>> I have been working around ceph quite a long and trying to stitch
>> zfs with
>> ceph. I was able to do it to certain extent as follows:
>> 1. zpool creation
>> 2. set dedup
>> 3. create a mountable volume of zfs (zfs create)
>> 4. format the volume with ext4 and enabling xattr
>> 5. mkcephfs on the volume
>>
>> This actually works and dedup is perfect. But i need to avoid
>> multiple layers
>> on the storage since the performance is very slow and the kernel
>> timeout
>> occurs often for a 8GB RAM. I want to test the performance between
>> btrfs and
>> zfs. I want to avoid the above multiple layering on storage and make
>> the ceph
>> cluster aware of zfs. Let me know if anyone has workaround this.
>
> I'm not familiar enough with zfs to know what 'mountable volume'
> means..
> is that a block device/lun that you're putting ext4 on? Probably the
> best
> results will come from creating a zfs *file system* (using the ZPL or
> whatever it is) and running ceph-osd on top of that.
>
> There is at least one open bug from someone having problems there,
> but
> we'd very much like to sort out the problem.
>
> sage
prev parent reply other threads:[~2012-10-26 5:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <441865dbf9e127f0b85193c512878a76@iihtcloudsolutions.com>
2012-10-25 15:36 ` [ceph-commit] Ceph Zfs Sage Weil
2012-10-26 4:46 ` Raghunandhan
2012-10-26 19:38 ` Dan Mick
2012-10-27 5:14 ` Raghunandhan
2012-10-27 17:15 ` Sage Weil
2012-10-28 5:19 ` Raghunandhan
2012-10-27 5:50 ` Raghunandhan
2012-10-26 5:32 ` Raghunandhan [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=1e5cd344bedc185dd0cf7a930790bc6a@iihtcloudsolutions.com \
--to=raghunandhan.g@iihtcloudsolutions.com \
--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.