CEPH filesystem development
 help / color / mirror / Atom feed
From: Stefan Priebe <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: Fri, 02 Nov 2012 21:13:23 +0100	[thread overview]
Message-ID: <50942963.1020700@profihost.ag> (raw)
In-Reply-To: <5093F1F6.5040502@inktank.com>


>> [   75.480358] end_request: I/O error, dev sdc, sector 50331642
>> [   75.496374] sd 2:0:0:4: [sdc]
>> [   75.497202] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
>> [   75.498077] sd 2:0:0:4: [sdc]
>> [   75.498948] Sense Key : Aborted Command [current]
>> [   75.499818] sd 2:0:0:4: [sdc]
>> [   75.500374] Add. Sense: I/O process terminated
>> [   75.500374] sd 2:0:0:4: [sdc] CDB:
>> [   75.500374] Write same(16): 93 08 00 00 00 00 03 7f ff f9 00 7f ff ff
>> 00 00
>> [   75.500374] end_request: I/O error, dev sdc, sector 58720249
>
> Could you add 'debug ms = 1', 'debug rbd = 20', and 'log file =
> /tmp/librbd.log' to the [client] section of your ceph.conf?
>
> That log should tell us where the error is happening.

Thanks - here it comes:
https://www.dropbox.com/s/blegk8u14n30ntq/librbd.log.gz

Hope that helps and we can fix it before 0.54.

Greets
Stefan

  reply	other threads:[~2012-11-02 20:13 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 [this message]
2012-11-03 18:47           ` Stefan Priebe
2012-11-06  8:09             ` Stefan Priebe - Profihost AG
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=50942963.1020700@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