There are hardware problems here...
[112531.319224] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[112531.319231] ata4.00: failed command: WRITE DMA EXT
[112531.319240] ata4.00: cmd 35/00:00:00:8d:46/00:04:08:00:00/e0 tag 0
dma 524288 out
res 40/00:00:00:00:00/00:00:00:00:00/40 Emask
0x4 (timeout)
It's not ever good when a write command fails. It should take less
than 10 seconds for the drive to figure out if a sector is
persistently bad and to remap it. Yet it times out. I'm not sure why
though.
[112531.319243] ata4.00: status: { DRDY }
[112531.319252] ata4: hard resetting link
[112536.867209] ata4: link is slow to respond, please be patient (ready=0)
[112541.365663] ata4: SRST failed (errno=-16)
[112541.365672] ata4: hard resetting link
[112546.913747] ata4: link is slow to respond, please be patient (ready=0)
[112551.412202] ata4: SRST failed (errno=-16)
[112551.412211] ata4: hard resetting link
[112556.960286] ata4: link is slow to respond, please be patient (ready=0)
[112570.995495] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[112571.036455] ata4.00: configured for UDMA/133
[112571.036464] ata4.00: device reported invalid CHS sector 0
[112571.036474] ata4: EH complete
[112601.295099] ata4: lost interrupt (Status 0x51)
So it all gets reset...
[112601.295121] ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x40d0002
action 0xe frozen
[112601.295126] ata4: SError: { RecovComm PHYRdyChg CommWake 10B8B DevExch }
[112601.295130] ata4.00: failed command: WRITE DMA EXT
[112601.295138] ata4.00: cmd 35/00:00:00:ff:4e/00:04:08:00:00/e0 tag 0
dma 524288 out
res 40/00:00:00:00:00/00:00:00:00:00/40 Emask
0x14 (ATA bus error)
But it has another write failure and this time it's associated with a
bus error. So I don't know if this is a misbehaving drive that's
pissing off the controller, or if it's a bad cable (typically it's the
connector not the cable itself that goes bad).
[112601.295141] ata4.00: status: { DRDY }
[112601.295150] ata4: hard resetting link
[112602.204775] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[112602.265984] ata4.00: configured for UDMA/133
[112602.265990] ata4.00: device reported invalid CHS sector 0
More resetting.
[112641.561198] INFO: task kworker/u8:5:8631 blocked for more than 120 seconds.
[112641.561203] Not tainted 4.1.0-gentoo-r1 #1
[112641.561204] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[112641.561207] kworker/u8:5 D 0000000000015b40 0 8631 2 0x00000000
[112641.561222] Workqueue: writeback bdi_writeback_workfn (flush-btrfs-13)
and then hanging and more stuff...
Anyway it looks like it's hardware related, but I don't know what
device ata4.00 is, so maybe this helps:
http://superuser.com/questions/617192/mapping-ata-device-number-to-logical-device-name
---
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
