--FFhXKQi4mYVCUPkj
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi guys, I'm on the list and I read it all the time so no cc required.

Well, it is working, I rebuilt the parity a few times, and I the=20
reconstructed RAID twice...=20

The error messages still appear, but, everything is working, I'm happy
with that, as long as my data is safely copying from one disk to the
other.

Should I be concerned about this?


I included this in sys/dev/ata/wd.c with other similar entries.

        { "ST3160211A*",
          WD_QUIRK_FORCE_LBA48 },

Could it be the other quirk? The WD_QUIRK_SPLIT_MOD15_WRITE thingums?
Let me know if I must try this.

Thanks in advance.

On Sun, Mar 25, 2007 at 04:38:51PM +0200, Manuel Bouyer wrote:
> On Sun, Mar 25, 2007 at 09:31:32AM -0400, Greg Troxel wrote:
> >=20
> > I was reacting to William's error message:
> >=20
> >   wd2a: device timeout reading fsbn 268435392 of 268435392-268435519 (w=
d2 bn 268435455; cn 266305 tn 0 sn 15), retrying
> >   pdcsata0:0:0: lost interrupt type: ata tc_bcount: 65536 tc_skip: 0
> >=20
> > That transfer is FFFFFC0 to 1000003F, so it looks like it crosses the
> > boundary.  Does the code switch to LBA48 for the whole transfer?  Does
> > it need to be split into a non-LBA48 and a LB48 part?  Perhaps the
> > drive can't handle such crossings.  I could be off by some power of
> > two, though.
>=20
> Yes, this one cross the LBA48 barrier. But in previous messages he inclued
> errors with other block numbers ...
>=20
> --=20
> Manuel Bouyer <bouyer@antioche.eu.org>
>      NetBSD: 26 ans d'experience feront toujours la difference
> --

--=20
Omina Solutions  | http://omina.co.za | (012) Ph. 664-2480 F. 664-2474=20


--FFhXKQi4mYVCUPkj
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (NetBSD)

iD8DBQFGBrms0o1hk/SHCkoRArrBAKCqQogF2raYvq/5lUAbIsxnFB8sygCeOGdL
8Y5m3VUo4DAhIuS8ruQafMc=
=Agu0
-----END PGP SIGNATURE-----

--FFhXKQi4mYVCUPkj--