From: Alex Elder <elder@ieee.org>
To: Hannes Landeholm <hannes@jumpstarter.io>,
Ilya Dryomov <ilya.dryomov@inktank.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Cc: Thorwald Lundqvist <thorwald@jumpstarter.io>
Subject: Re: crash in rbd_img_request_create
Date: Tue, 13 May 2014 12:18:18 -0500 [thread overview]
Message-ID: <537253DA.4030903@ieee.org> (raw)
In-Reply-To: <CABt9es_dd3VjuBaHUkM9qRW6aJDujHE3yN1FvkojtXXXQhcsqQ@mail.gmail.com>
On 05/13/2014 12:17 PM, Hannes Landeholm wrote:
> On Tue, May 13, 2014 at 2:35 PM, Alex Elder <elder@ieee.org> wrote:
>> On 05/12/2014 12:28 PM, Hannes Landeholm wrote:
>>> We where experimenting to use ZFS as a backend for
>>> CEPH just to see what the performance and storage saving
>>> characteristics was like but we're gonna completely switch to ext4 now
>>> and see if the problem goes away.
>>
>> This is very good to know. Please report back what you find.
>
> We completely cleansed the server in question from any trace of ZFS
> and ran the same test again with ext4 instead for the ceph backend
> with the same conditions. Everything worked fine. The machine has also
> stopped randomly locking up. We will not touch ZFS again. Maybe in a
> distant future where it actually integrates well with Linux.
That's good news for rbd... Thanks a lot. -Alex
> Thank you for your time,
> Hannes
>
next prev parent reply other threads:[~2014-05-13 17:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 22:18 crash in rbd_img_request_create Hannes Landeholm
2014-05-11 3:11 ` Alex Elder
2014-05-11 9:33 ` Ilya Dryomov
2014-05-12 4:34 ` Alex Elder
2014-05-12 17:28 ` Hannes Landeholm
2014-05-13 12:35 ` Alex Elder
2014-05-13 17:17 ` Hannes Landeholm
2014-05-13 17:18 ` Alex Elder [this message]
2014-05-13 20:58 ` Sage Weil
2014-05-13 21:39 ` Hannes Landeholm
2014-05-11 16:33 ` Hannes Landeholm
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=537253DA.4030903@ieee.org \
--to=elder@ieee.org \
--cc=ceph-devel@vger.kernel.org \
--cc=hannes@jumpstarter.io \
--cc=ilya.dryomov@inktank.com \
--cc=thorwald@jumpstarter.io \
/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.