Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 2 Nov 2007 10:52:06 +0100
From:      Pawel Jakub Dawidek <pjd@FreeBSD.org>
To:        Thierry Herbelot <thierry@herbelot.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: regression with gmirror, Promise SATA and 7.0 ?
Message-ID:  <20071102095206.GB24455@garage.freebsd.pl>
In-Reply-To: <200711011509.46094.thierry@herbelot.com>
References:  <200711011509.46094.thierry@herbelot.com>

next in thread | previous in thread | raw e-mail | index | archive | help

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

On Thu, Nov 01, 2007 at 03:09:45PM +0100, Thierry Herbelot wrote:
> Hello,
>=20
> I have tried to switch my home server from a 6.3-PRERELEASE to the latest=
=20
> 7.0-BETA1.5-i386-disc1.iso.
>=20
> I have loopback-mounted the iso and unarchived the base and kernel to a n=
ew=20
> gmirrored partition hosted on two "Seagate ST3250823AS" SATA disks connec=
ted=20
> via a "Promise PDC40518 SATA150" controller.
>=20
> after rebooting to the new "current" gmirror partition, any disk access g=
ives=20
> errors such as :
> ad6: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=3D58616578
> ad6: FAILURE - device detached
> subdisk6: detached
> ad6: detached
> GEOM_MIRROR: Cannot write metadata on ad6s3 (device=3Dgm0s3, error=3D6).
> GEOM_MIRROR: Cannot update metadata on disk ad6s3 (error=3D6).
> GEOM_MIRROR: Device gm0s4: provider ad6s4 disconnected.
> GEOM_MIRROR: Device gm0s2: provider ad6s2 disconnected.
> GEOM_MIRROR: Device gm0s1: provider ad6s1 disconnected.
> ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - complet=
ing=20
> request directly
> ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - complet=
ing=20
> request directly
> ad10: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing=
=20
> request directly
> ad10: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing=
=20
> request directly
> ad10: WARNING - SET_MULTI taskqueue timeout - completing request directly
> ad10: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=3D62894473
> GEOM_MIRROR: Cannot update metadata on disk ad6s3 (error=3D6).
> GEOM_MIRROR: Device gm0s3: provider ad6s3 disconnected.
> g_vfs_done():mirror/gm0s3f[READ(offset=3D5429510144, length=3D65536)]erro=
r =3D 6
> vnode_pager_getpages: I/O read error
>=20
> The same ad6 and ad10 disks are presently used under 6.x without any (vis=
bile)=20
> errors (and have been for more than one year).
>=20
> Thus, it seems that the combination of this Promise controller and the SA=
TA=20
> disks has issues (there was a thread about Promise controllers and ZFS, b=
ut=20
> with no clear conclusion).

Just to clarify. There is no regression in gmirror. This is ATA
problem/bug, which was reported so many times already.

> PS : I was also burnt by the forced conversion of gmirror metadata from v=
3 to=20
> v4, which makes it tricky to backtrack to 6.x, once a 7.x kernel + gmirro=
r=20
> has been booted once.

I'm not happy with with metadata auto-upgrade, but it just makes things
so much easier. You can always boot your 6.x to single-user mode using
disk directly (it should not change anything on disk) and just run
'gmirror label' again.

--=20
Pawel Jakub Dawidek                       http://www.wheel.pl
pjd@FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFHKvNGForvXbEpPzQRAh4+AJ0Rw7RgR2JNTyZfyOCHZwHjqDREsQCgy3Su
CNKYQV6v1pI8dr9GO2CwPH8=
=aFsv
-----END PGP SIGNATURE-----

--TakKZr9L6Hm6aLOc--



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