All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Simon Dray <sdray@Espial.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS issue xfs goes offline with various messages drive not recoverable without reboot
Date: Thu, 02 Oct 2014 14:40:36 -0500	[thread overview]
Message-ID: <542DAA34.4090701@sandeen.net> (raw)
In-Reply-To: <FC1F5573-DA27-4E68-98CA-B5CE63DACE3D@Espial.com>

Yes, something went wrong w/ storage, lost IOs, and xfs is reacting - 
telling you about the problems it encountered as a result.

-Eric

On 10/2/14 12:30 PM, Simon Dray wrote:
> Eric
> 
> So would you say this is hardware
> 
> Thanks for looking 
> 
> Regards Simon
> 
> Simon Dray
> Espial (UK)
> sdray@espial.com
> Tel: +441223716476
> 
> 
>> On 2 Oct 2014, at 16:37, Eric Sandeen <sandeen@sandeen.net> wrote:
>>
>> On 10/2/14 6:05 AM, Simon Dray wrote:
>>
>> ...
>>> CE: hpet increasing min_delta_ns to 40226 nsec
>>> hpsa 0000:03:00.0: Abort request on C3:B0:T0:L4
>>> hpsa 0000:03:00.0: cp ffff8800bd3ee000 is reported invalid (probably means target device no longer present)
>>> hpsa 0000:03:00.0: cp ffff8800bd3ee000 is reported invalid (probably means target device no longer present)
>>> hpsa 0000:03:00.0: FAILED abort on device C3:B0:T0:L4
>>> hpsa 0000:03:00.0: resetting device 3:0:0:4
>>> hpsa 0000:03:00.0: cp ffff8800bd3ee000 is reported invalid (probably means target device no longer present)
>>> hpsa 0000:03:00.0: resetting device failed.
>>> sd 3:0:0:4: Device offlined - not ready after error recovery
>>> sd 3:0:0:4: [sde] Unhandled error code
>>> sd 3:0:0:4: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT
>>> sd 3:0:0:4: [sde] CDB: Write(16): 8a 00 00 00 00 02 39 90 e9 60 00 00 0c 08 00 00
>>> sd 3:0:0:4: rejecting I/O to offline device
>>> sd 3:0:0:4: [sde] killing request
>>> sd 3:0:0:4: rejecting I/O to offline device
>>> sd 3:0:0:4: rejecting I/O to offline device
>>> sd 3:0:0:4: rejecting I/O to offline device
>>> sd 3:0:0:4: rejecting I/O to offline device
>> ...
>>> sd 3:0:0:4: [sde] Unhandled error code
>>> sd 3:0:0:4: [sde] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
>>> sd 3:0:0:4: [sde] CDB: Write(10): 2a 00 b6 43 28 00 00 0c 98 00
>>> Buffer I/O error on device md0, logical block 3583397932
>>> lost page write due to I/O error on md0
>>> Buffer I/O error on device md0, logical block 3583397933
>>> lost page write due to I/O error on md0
>> ...
>>
>> It looks like you need to address your storage issues first, and then see what if any repair needs to be done on the xfs filesystem.
>>
>> -Eric
> 
> _______________________________________________
> 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

  reply	other threads:[~2014-10-02 19:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25  7:30 XFS issue xfs goes offline with various messages drive not recoverable without reboot Simon Dray
2014-09-25  8:12 ` Dave Chinner
2014-10-02 11:05   ` Simon Dray
2014-10-02 15:37     ` Eric Sandeen
2014-10-02 17:30       ` Simon Dray
2014-10-02 19:40         ` Eric Sandeen [this message]
2014-10-02 19:42           ` Simon Dray

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=542DAA34.4090701@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=sdray@Espial.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 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.