From: Kernel Panic <cinap_lenrek@gmx.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work
Date: Wed, 6 Feb 2008 11:43:47 +0100 [thread overview]
Message-ID: <47A98F63.2030301@gmx.de> (raw)
In-Reply-To: <04c53dc9441e182cb7a9b176ff73a81d@coraid.com>
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
next prev parent reply other threads:[~2008-02-06 10:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 22:13 cinap_lenrek
2008-02-06 8:41 ` Kernel Panic
2008-02-06 9:45 ` erik quanstrom
2008-02-06 10:43 ` Kernel Panic [this message]
2008-02-06 11:03 ` erik quanstrom
[not found] <54b639a7eb08c31e4ef2a6d9fd7b6a62@quanstro.net>
2008-02-08 9:35 ` Kernel Panic
2008-02-08 14:55 ` erik quanstrom
2008-02-08 14:56 ` Robert Raschke
2008-02-08 15:27 ` Robert Raschke
-- strict thread matches above, loose matches on Subject: below --
2008-02-06 17:58 [9fans] usb ohci support arrives -- another caution Sape Mullender
2008-02-06 19:23 ` [9fans] VIA VT8237 SATA/RAID i/o errors, dma doesnt work cinap_lenrek
2008-02-06 20:04 ` erik quanstrom
2008-02-06 22:29 ` cinap_lenrek
2008-02-06 22:40 ` erik quanstrom
2008-02-06 23:26 ` cinap_lenrek
2008-02-05 8:18 Kernel Panic
2008-02-05 8:54 ` Lorenzo Fernando Bivens de la Fuente
2008-02-05 13:20 ` erik quanstrom
2008-02-05 19:48 ` Robert Raschke
2008-02-06 2:01 ` arisawa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47A98F63.2030301@gmx.de \
--to=cinap_lenrek@gmx.de \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).