Re: [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work

cinap_lenrek@gmx.de wrote:
>wrtest1 /dev/sdD0/9hal.m.varena
>wrtest2 /dev/sdD0/9hal.m.varena
>rwtest2 /dev/sdD0/9hal.m.varena
>
>well, seems to work fine!
>
>
maybe a little bit too early... ran venti/wrarena on sdC0
last night and in the morining the system was completly freezed.
(disk led was off, screen was blank)

:-(

seems that my dd tests are too simple or run too shortly...
i'll attach serial console to the machine and try to reproduce it.

cinap

Re: [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work

> maybe a little bit too early... ran venti/wrarena on sdC0
> last night and in the morining the system was completly freezed.
> (disk led was off, screen was blank)
>
> :-(
>
> seems that my dd tests are too simple or run too shortly...
> i'll attach serial console to the machine and try to reproduce it.
>
> cinap

you may want to try a block size of 64k in your tests.
this may make a difference.

- erik

Re: [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work

erik quanstrom wrote:
>you may want to try a block size of 64k in your tests.
>this may make a difference.
>
>
thats exactly what the dd based testscript does:

fn rotest {
....
dd -if $1 -of /dev/null -bs $3 &
....
}

....
b=65536

rotest $d $t $b
....

i choose that blocksize because the I/O erros printed by venti
while i first tried to copy arenas showed that blocksize.

i conclude for now that doing paralel io on both drives results
in I/O errors in short time. reading/writing a single drive, the
system hangs/freezes after many hours without a trace.

>- erik
>
>
cinap

Re: [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work

> i choose that blocksize because the I/O erros printed by venti
> while i first tried to copy arenas showed that blocksize.
>
> i conclude for now that doing paralel io on both drives results
> in I/O errors in short time. reading/writing a single drive, the
> system hangs/freezes after many hours without a trace.
>

eh. sorry for the stupid suggestion. have you tried reducing the
size of the reads? does it still hang with a 32k blocksize? perhaps
plan 9 is too fast. :-).