Re: spec_getpages I/O read failure on md0

2003-01-02 Thread phk
In message [EMAIL PROTECTED], Bruce Evans writes: The md driver doesn't set any of the si_ size parameters so it has no chance of getting this stuff right when the parameters are not the defaults. It does however set its sectorsize to 4k. The problem was GEOM not setting si_bsize_phys on the

Re: spec_getpages I/O read failure on md0

2003-01-02 Thread Bruce Evans
On Thu, 2 Jan 2003 [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], Bruce Evans writes: The md driver doesn't set any of the si_ size parameters so it has no chance of getting this stuff right when the parameters are not the defaults. It does however set its sectorsize to 4k. The

Re: spec_getpages I/O read failure on md0

2003-01-02 Thread phk
In message [EMAIL PROTECTED], Bruce Evans writes: On Thu, 2 Jan 2003 [EMAIL PROTECTED] wrote: In message [EMAIL PROTECTED], Bruce Evans writes: The md driver doesn't set any of the si_ size parameters so it has no chance of getting this stuff right when the parameters are not the defaults.

Re: spec_getpages I/O read failure on md0

2002-12-30 Thread Jos Backus
I was finally able to reproduce this. Here are some offset values: Dec 30 10:55:07 lizzy kernel: spec_getpages:(md0) I/O read failure: (error=22) b p 0xce5fb488 vp 0xc41e4708 Dec 30 10:55:07 lizzy kernel: size: 6144, resid: 6144, a_count: 6124, valid: 0x0 Dec 30 10:55:07 lizzy kernel: nread: 0

spec_getpages I/O read failure on md0

2002-12-28 Thread Jos Backus
01:43:26 lizzy kernel: spec_getpages:(md0) I/O read failure: (error=22) bp 0xce5fb158 vp 0xc41e8708 Dec 28 01:43:26 lizzy kernel: size: 14848, resid: 14848, a_count: 14404, valid: 0x0 Dec 28 01:43:26 lizzy kernel: nread: 0, reqpage: 0, pindex: 0, pcount: 4 This is with FreeBSD

Re: spec_getpages I/O read failure on md0

2002-12-28 Thread phk
In message [EMAIL PROTECTED], Jos Backus writes: Accompanied by Dec 28 01:42:12 lizzy kernel: spec_getpages:(md0) I/O read failure: (error=22) bp 0xce5f9310 vp 0xc41e8708 Dec 28 01:42:12 lizzy kernel: size: 2048, resid: 2048, a_count: 2028, valid: 0x0 Dec 28 01:42:12 lizzy kernel

Re: spec_getpages I/O read failure on md0

2002-12-28 Thread Jos Backus
On Sat, Dec 28, 2002 at 08:39:32PM +0100, [EMAIL PROTECTED] wrote: 22 is EINVAL, so likely cause is a bogus offset. Either unaligned or out of range. Unfortunately the above messages does not contain the offset of the I/O operation. Suggest you ammend one or more of the relevant printfs to

Re: spec_getpages I/O read failure on md0

2002-12-28 Thread phk
In message [EMAIL PROTECTED], Jos Backus writes: On Sat, Dec 28, 2002 at 08:39:32PM +0100, [EMAIL PROTECTED] wrote: 22 is EINVAL, so likely cause is a bogus offset. Either unaligned or out of range. Unfortunately the above messages does not contain the offset of the I/O operation. Suggest

Re: spec_getpages I/O read failure on md0

2002-12-28 Thread Bruce Evans
install -s -o root -g wheel -m 555 ispcvt /usr/sbin install -o root -g wheel -m 444 ispcvt.8.gz /usr/share/man/man8 === usr.sbin/pcvt/vgaio echo:Input/output error *** Error code 1 ... Accompanied by Dec 28 01:42:12 lizzy kernel: spec_getpages:(md0) I/O read failure: (error

Re: spec_getpages I/O read failure on md0

2002-12-28 Thread Jos Backus
On Sun, Dec 29, 2002 at 03:57:49PM +1100, Bruce Evans wrote: Errors caused by these bugs can be non-deterministic because the pages may be loaded into memory other means. E.g., when exec off zip drives was broken, exec would succeed after several attempts because each attempt loaded another 8