Jul 17 06:55:13 black kernel: sd 2:0:0:0: [sda] Write cache: enabled,
read cache: enabled, doesn't support DPO or FUA
Jul 17 06:55:13 black kernel: sd 12:0:0:0: [sdb] Write cache: enabled,
read cache: enabled, doesn't support DPO or FUA
Jul 17 06:55:13 black kernel: sd 13:0:1:0: [sdc] Write cache: enabled,
read cache: enabled, doesn't support DPO or FUA
I see this often, even with direct connect SATA SSD's of recent
vintage (like a Samsung 840 EVO I have).
Jul 17 23:19:52 black kernel: ata10.00: exception Emask 0x1 SAct 0x0
SErr 0x0 action 0x0
Jul 17 23:19:52 black kernel: ata10.00: irq_stat 0x40000001
Jul 17 23:19:52 black kernel: ata10.00: cmd
a0/01:00:00:00:01/00:00:00:00:00/a0 tag 3 dma 16640 in
opcode=0x12 12 01 80 00 ff
00res 40/00:00:00:00:00/00:00:00:00:00/10 Emask 0x1 (device error)
Jul 17 23:19:52 black kernel: ata10.00: status: { DRDY }
Jul 17 23:19:52 black kernel: ata10.00: exception Emask 0x1 SAct 0x0
SErr 0x0 action 0x0
Jul 17 23:19:52 black kernel: ata10.00: irq_stat 0x40000001
Jul 17 23:19:52 black kernel: ata10.00: cmd
a0/01:00:00:00:01/00:00:00:00:00/a0 tag 4 dma 16640 in
opcode=0x1a 1a 00 3f 00 ff
00res 40/00:00:00:00:00/00:00:00:00:00/10 Emask 0x1 (device error)
Jul 17 23:19:52 black kernel: ata10.00: status: { DRDY }
Jul 17 23:19:52 black kernel: ata10: exception Emask 0x1 SAct 0x0 SErr
0x0 action 0x0
Jul 17 23:19:52 black kernel: ata10: irq_stat 0x40000001
You've got device problems. I'm not sure if it's the drive,
controller, or cabling.
ls -l /sys/block should help figure out if ata10 is actually sd
target 13:0:1:0 which is what matches up wth sdc, which is what Btrfs
is faceplanting on.
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
