Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 28 Dec 2002 20:39:32 +0100
From:      phk@FreeBSD.ORG
To:        jos@catnook.com
Cc:        freebsd-current@FreeBSD.ORG
Subject:   Re: spec_getpages I/O read failure on md0 
Message-ID:  <87915.1041104372@critter.freebsd.dk>
In-Reply-To: Your message of "Sat, 28 Dec 2002 11:34:09 PST." <20021228193431.GA13948@lizzy.catnook.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <20021228193431.GA13948@lizzy.catnook.com>, 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: nread: 0, reqpage: 0, pindex: 1, pcount: 1
>    Dec 28 01:42:12 lizzy kernel: vm_fault: pager read error, pid 40673 (sh)
>    Dec 28 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

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 also printout
the offset at which the I/O operation was attempted.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87915.1041104372>