Date: Mon, 29 Jul 2002 08:14:33 -0400 (EDT) From: John Baldwin <jhb@FreeBSD.org> To: Stuart Barkley <stuartb@4gh.net> Cc: Ian Dowse <iedowse@maths.tcd.ie>, freebsd-stable@FreeBSD.ORG Subject: Re: READ_BIG problems Message-ID: <XFMail.20020729081433.jhb@FreeBSD.org> In-Reply-To: <20020729044910.X69603-100000@precipice.4gh.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29-Jul-2002 Stuart Barkley wrote: > I continue to see the READ_BIG problems on my 4.6.1 test system. > > I've just finished a round of testing where I re-cvsup'ed with > tag=RELENG_4_6 and applied the patches suggested below. > > After rebuilding and reinstalling (just the kernel, using 4.6-RELEASE > userland) I now see rare, but still occasional READ_BIG errors. > > For testing I'm using a CD-R with 4.6-RELEASE mounted on /cdrom and > use the following commands: > > root@nick-3% find -s . -print0 | xargs -0 md5 > ~/4.6.md5.4 > root@nick-4% find -s . -print0 | xargs -0 md5 > ~/4.6.md5.5 > md5: ./packages/www/xswallow-1.0.18.tgz: Input/output error > root@nick-5% > > On my most recent build I have received a single READ_BIG error on > each of two runs of the command: > > Jul 29 03:42:43 nick /kernel: acd0: READ_BIG - ILLEGAL REQUEST asc=0x64 ascq=0x00 error=0x00 > Jul 29 04:42:00 nick /kernel: acd0: READ_BIG - ILLEGAL REQUEST asc=0x64 ascq=0x00 error=0x00 This is a different READ_BIG than the one others were seeing (command timeout) and could be an indication of bad media. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20020729081433.jhb>