Re: wd0 read timeouts - how to proceed?

2010-12-24 Thread Gabriel Linder
On 12/24/10 17:09, Chris Smith wrote: On Fri, Dec 24, 2010 at 5:00 AM, Webcharge wrote: Is this the actual disk or the controller/other hardware? If the hardware is "smart" aware installing smartmontools and running smartctl may give you a clue. atactl(8) works just fine.

Re: wd0 read timeouts - how to proceed?

2010-12-24 Thread Chris Smith
On Fri, Dec 24, 2010 at 5:00 AM, Webcharge wrote: > Is this the actual disk or the controller/other hardware? If the hardware is "smart" aware installing smartmontools and running smartctl may give you a clue.

Re: wd0 read timeouts - how to proceed?

2010-12-24 Thread Vadim Zhukov
2010/12/24 Joachim Schipper : > something like 'tar cpf - | tar xpf -' is more likely to get you a > somewhat consistent view. POSIX pax(1) with -rw options should work slightly faster (and it's already faster to type ;) ). -- WBR, Vadim Zhukov

Re: wd0 read timeouts - how to proceed?

2010-12-24 Thread Joachim Schipper
On Fri, Dec 24, 2010 at 11:00:48AM +0100, Webcharge wrote: > Must be the holiday season *sigh* my OpenBSD server is suddenly > giving the occassional read-timeout on the /var slice of the main > harddisk: > There is a second harddisk installed, with OpenBSD formatted slices, > but of different

wd0 read timeouts - how to proceed?

2010-12-24 Thread Webcharge
Must be the holiday season *sigh* my OpenBSD server is suddenly giving the occassional read-timeout on the /var slice of the main harddisk: --- wd0(pciide0:0:0): timeout type: ata c_bcount: 65536 c_skip: 0 wd0g: device timeout reading fsbn 17002464 of 17002464-170