RFC: ATA to CAM integration patch (INTEL DX58SO)

[Scott Long]

On Mon, 6 Jul 2009, Mike Tancsa wrote:

> At 02:41 AM 7/5/2009, Alexander Motin wrote:
>>> Jul  4 20:25:57 ich10 kernel: ahcich2: ahci_ch_intr ERROR is 40000001 cs 
>>> 00000004 ss 00000000 rs 00000004 tfd 451 serr 00000000
>> 
>> This is AHCI driver debugging. I've removed it in latest patch. In this 
>> case it means that drive signals some command error.
>
>
> Hi,
>
> With the latest patch (cam-ata.20090704.patch), writing to the disk with 
> physical errors looks like this now
>
> Jul  6 13:56:17 ich10 last message repeated 4 times
> Jul  6 13:56:17 ich10 kernel: g_vfs_done():ada2[READ(offset=42003431424, 
> length=16384)]error = 5
> Jul  6 13:56:17 ich10 kernel: ahcich2: Error while READ LOG EXT
> Jul  6 13:56:17 ich10 last message repeated 4 times
> Jul  6 13:56:17 ich10 kernel: g_vfs_done():ada2[READ(offset=42196107264, 
> length=16384)]error = 5
> Jul  6 13:56:17 ich10 kernel: ahcich2: Error while READ LOG EXT
> Jul  6 13:56:17 ich10 last message repeated 4 times
> Jul  6 13:56:17 ich10 kernel: g_vfs_done():ada2[READ(offset=42388783104, 
> length=16384)]error = 5
> Jul  6 13:56:17 ich10 kernel: ahcich2: Error while READ LOG EXT
> Jul  6 13:56:17 ich10 last message repeated 4 times
> Jul  6 13:56:17 ich10 kernel: g_vfs_done():ada2[READ(offset=42581458944, 
> length=16384)]error = 5
> Jul  6 13:56:17 ich10 kernel: ahcich2: Error while READ LOG EXT
> Jul  6 13:56:17 ich10 last message repeated 4 times
> Jul  6 13:56:17 ich10 kernel: g_vfs_done():ada2[READ(offset=42774134784, 
> length=16384)]error = 5
> Jul  6 13:56:17 ich10 kernel: ahcich2: Error while READ LOG EXT
> Jul  6 13:56:18 ich10 last message repeated 4 times
> Jul  6 13:56:18 ich10 kernel: g_vfs_done():ada2[READ(offset=42966810624, 
> length=16384)]error = 5
> Jul  6 13:56:18 ich10 kernel: ahcich2: Error while READ LOG EXT
> Jul  6 13:56:18 ich10 last message repeated 4 times
>
> Still the box does a panic when writing to the disk that has bad sectors on 
> it. (I do newfs it between reboots).   Again, not sure if this is a "well, 
> dont use a bad disk", but here is the panic again in case it shows something 
> useful.
>

This is a 'don't use a bad disk' panic; FreeBSD UFS and VM simply can't 
handle errors on reads or writes.

Scott