From: Eric Sandeen <sandeen@sandeen.net>
To: Jevon Qiao <qiaojianfeng@unitedstack.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: Ask help on an issue 'XFS (sd*): discard failed for extent, error 5'
Date: Tue, 1 Sep 2015 07:24:37 -0500 [thread overview]
Message-ID: <55E59905.80105@sandeen.net> (raw)
In-Reply-To: <55E53C84.1040606@unitedstack.com>
On 9/1/15 12:49 AM, Jevon Qiao wrote:
> Hi Eric
>
> Thank you very much for the prompt response.
> On 1/9/15 12:28, Eric Sandeen wrote:
>> On 8/31/15 10:55 PM, Jevon Qiao wrote:
>>> Hi All,
>>>
>>> Currently, I notice that there are lot's of errors written in the /var/log/messages file.
>>>
>>> 2015-08-29T23:58:54.477236+00:00 server-68 kernel: sd 0:0:4:0: [sdc]
>>> 2015-08-29T23:58:54.477255+00:00 server-68 kernel: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
>>> 2015-08-29T23:58:54.477256+00:00 server-68 kernel: sd 0:0:4:0: [sdc]
>>> 2015-08-29T23:58:54.477257+00:00 server-68 kernel: Sense Key : Illegal Request [current]
>>> 2015-08-29T23:58:54.477258+00:00 server-68 kernel: sd 0:0:4:0: [sdc]
>>> 2015-08-29T23:58:54.477259+00:00 server-68 kernel: Add. Sense: Invalid field in parameter list
>>> 2015-08-29T23:58:54.477260+00:00 server-68 kernel: sd 0:0:4:0: [sdc] CDB:
>>> 2015-08-29T23:58:54.477261+00:00 server-68 kernel: Unmap/Read sub-channel: 42 00 00 00 00 00 00 00 18 00
>>> 2015-08-29T23:58:54.477263+00:00 server-68 kernel: end_request: critical target error, dev sdc, sector 325046824
>>> 2015-08-29T23:58:54.477268+00:00 server-68 kernel: XFS (sdc2): discard failed for extent [0x64815,2021], error 5
>>>
>>> Has anyone encountered the same issue before? How can you solve it?
>> Looks like xfs is simply reacting to errors from the storage; I'd try to get
>> to the bottom of why you're getting all those scsi errors.
> I just want to understand the meaning of 'XFS (sdc2): discard failed
> for extent [0x64815,2021], error 5', does it mean one of the layers
> beneath xfs does not support DISCARD? Could you please show me more
> clues?
"error 5" is EIO. That's as much as I can tell you from the XFS perspective.
I don't know what the block/scsi errors mean, exactly; it does seem as
if it may not support discard, but it must have advertised that it did, or
the discard would not have been issued in the first place.
You haven't said what kernel or storage you're on.
OTOH, even if you do, it's a scsi/storage issue that the xfs list probably
can't help much with.
-Eric
> Thanks,
> Jevon
>> But probably not on the xfs list. :)
>>
>> -Eric
>>
>>> Thanks,
>>> Jevon
>>>
>>>
>>> _______________________________________________
>>> xfs mailing list
>>> xfs@oss.sgi.com
>>> http://oss.sgi.com/mailman/listinfo/xfs
>>>
>> _______________________________________________
>> xfs mailing list
>> xfs@oss.sgi.com
>> http://oss.sgi.com/mailman/listinfo/xfs
>
>
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-09-01 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 3:55 Ask help on an issue 'XFS (sd*): discard failed for extent, error 5' Jevon Qiao
2015-09-01 4:28 ` Eric Sandeen
[not found] ` <55E53C84.1040606@unitedstack.com>
2015-09-01 12:24 ` Eric Sandeen [this message]
2015-09-02 1:33 ` Jevon Qiao
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=55E59905.80105@sandeen.net \
--to=sandeen@sandeen.net \
--cc=qiaojianfeng@unitedstack.com \
--cc=xfs@oss.sgi.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