xfs
[Top] [All Lists]

Re: XFS issue xfs goes offline with various messages drive not recoverab

To: Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject: Re: XFS issue xfs goes offline with various messages drive not recoverable without reboot
From: Simon Dray <sdray@xxxxxxxxxx>
Date: Thu, 2 Oct 2014 19:42:14 +0000
Accept-language: en-GB, en-US
Cc: "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <542DAA34.4090701@xxxxxxxxxxx>
References: <dd6d1d6e9fa7469584e72574347bb088@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20140925081254.GH4758@dastard> <dcbe632f22434828866c744247fcad08@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <542D712E.7050903@xxxxxxxxxxx> <FC1F5573-DA27-4E68-98CA-B5CE63DACE3D@xxxxxxxxxx>,<542DAA34.4090701@xxxxxxxxxxx>
Thread-index: AQHP2JiOlCHFKVSF30yUfVq4ZEQPRJwcrPTwgABPWgCAAAzyAIAANwgAgAAAdY4=
Thread-topic: XFS issue xfs goes offline with various messages drive not recoverable without reboot
Eric

thanks appreciate your time

Regards Simon



> On 2 Oct 2014, at 20:40, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
> 
> 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@xxxxxxxxxx
>> Tel: +441223716476
>> 
>> 
>>> On 2 Oct 2014, at 16:37, Eric Sandeen <sandeen@xxxxxxxxxxx> 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@xxxxxxxxxxx
>> http://oss.sgi.com/mailman/listinfo/xfs
>> 
> 

<Prev in Thread] Current Thread [Next in Thread>