yes indeed - referenced it in my update here
https://mail-archive.com/linux-btrfs@vger.kernel.org/msg47380.html

On 13 October 2015 at 13:04, Justin Maggard <jmaggar...@gmail.com> wrote:
> Sounds to me like this: https://bugzilla.kernel.org/show_bug.cgi?id=93581
>
> On Mon, Oct 12, 2015 at 11:37 AM, Chris Murphy <li...@colorremedies.com> 
> wrote:
>> I get a lot of these from both sdb and sdc
>>
>> Oct 11 23:00:03 cloud.warrenhughes.net kernel: sd 0:0:1:0: [sdb]
>> UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
>> Oct 11 23:00:03 cloud.warrenhughes.net kernel: sd 0:0:1:0: [sdb] Sense
>> Key : 0x3 [current]
>> Oct 11 23:00:03 cloud.warrenhughes.net kernel: sd 0:0:1:0: [sdb]
>> ASC=0x11 ASCQ=0x0
>> Oct 11 23:00:03 cloud.warrenhughes.net kernel: sd 0:0:1:0: [sdb] CDB:
>> opcode=0x88 88 00 00 00 00 00 11 b3 e1 98 00 00 00 08 00 00
>> Oct 11 23:00:03 cloud.warrenhughes.net kernel: blk_update_request:
>> critical medium error, dev sdb, sector 297001368
>>
>>
>>
>> Oct 11 23:47:32 cloud.warrenhughes.net kernel: sd 0:0:2:0: [sdc]
>> UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
>> Oct 11 23:47:32 cloud.warrenhughes.net kernel: sd 0:0:2:0: [sdc] Sense
>> Key : 0x3 [current] [descriptor]
>> Oct 11 23:47:32 cloud.warrenhughes.net kernel: sd 0:0:2:0: [sdc]
>> ASC=0x11 ASCQ=0x0
>> Oct 11 23:47:32 cloud.warrenhughes.net kernel: sd 0:0:2:0: [sdc] CDB:
>> opcode=0x88 88 00 00 00 00 01 3e 0a 7d 80 00 00 01 00 00 00
>> Oct 11 23:47:32 cloud.warrenhughes.net kernel: blk_update_request:
>> critical medium error, dev sdc, sector 5335842176
>>
>> There are a lot of these kinds of errors and they aren't all for the
>> same LBA +/- 8 so they're are different physical sectors affected on
>> both drives, but I don't know what the error is.
>>
>>
>> Oct 10 07:42:36 cloud.warrenhughes.net kernel: sd 0:0:1:0: [sdb]
>> 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
>> Oct 10 07:42:36 cloud.warrenhughes.net kernel: sd 0:0:1:0: [sdb]
>> 4096-byte physical blocks
>>
>> sd 0:0:1:0 starts out as sdb, but then goes a bit crazy somehow and
>> eventually gets offlined
>> Oct 11 23:55:24 cloud.warrenhughes.net kernel: sd 0:0:1:0: rejecting
>> I/O to offline device
>>
>> And then reappears as sdo
>>
>> Oct 11 23:57:56 cloud.warrenhughes.net kernel: sd 0:0:1:0: [sdo]
>> 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
>>
>> But no further scsi messages for this drive while Btrfs now complains
>> about sdo instead of sdb. Seems to me that this device is confused
>> even about its own error reporting. Anyway both sdb and sdc were
>> having problems at the same time.
>>
>>
>> Chris Murphy
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>> the body of a message to majord...@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
Warren Hughes
+64 21 633324
IM: gtalk + msn: this email address, skype: akawsh
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to