From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Josh Durgin <josh.durgin@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: RBD trim / unmap support?
Date: Tue, 06 Nov 2012 09:09:07 +0100 [thread overview]
Message-ID: <5098C5A3.60201@profihost.ag> (raw)
In-Reply-To: <509566BB.5030706@profihost.ag>
Am 03.11.2012 19:47, schrieb Stefan Priebe:
> Hi Josh,
>
>> Thanks - here it comes:
>> https://www.dropbox.com/s/blegk8u14n30ntq/librbd.log.gz
>
> It this one OK? Do you get an idea what this could be?
I checked this again today with latest git and wip-rbd-read branch but i
still get the same I/O errors.
Stefan
next prev parent reply other threads:[~2012-11-06 8:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 23:33 RBD trim / unmap support? Stefan Priebe
2012-11-01 23:36 ` Josh Durgin
2012-11-02 8:20 ` Stefan Priebe - Profihost AG
2012-11-02 8:21 ` Dietmar Maurer
2012-11-02 9:08 ` Stefan Priebe - Profihost AG
2012-11-02 14:18 ` Stefan Priebe - Profihost AG
2012-11-02 16:16 ` Josh Durgin
2012-11-02 20:13 ` Stefan Priebe
2012-11-03 18:47 ` Stefan Priebe
2012-11-06 8:09 ` Stefan Priebe - Profihost AG [this message]
2012-11-06 22:45 ` Stefan Priebe
2012-11-11 12:08 ` Stefan Priebe
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=5098C5A3.60201@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=josh.durgin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox