Date: Sun, 14 Oct 2007 10:37:38 -0500 (CDT) From: Lars Eighner <stableuser@larseighner.com> To: d_elbracht <d_elbracht@ecngs.de> Cc: freebsd-stable@freebsd.org, freebsd-geom@freebsd.org Subject: Re: g_vfs_done():da3s1a[READ(offset=81064794762854400, length=8192)]error = 5 Message-ID: <20071014103129.W19754@qroenaqrq.6qbyyneqvnyhc.pbz> In-Reply-To: <008801c80e65$47cbe650$639049d9@EC1a> References: <008801c80e65$47cbe650$639049d9@EC1a>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 14 Oct 2007, d_elbracht wrote: > we are trying to diagnose errors seen on 6.2, SMP, amd64, cvsup'ed of > 2007-10-09 > > Mainboard is a Tyan Thunder h2000M (S3992-E) with 16 GB RAM and 2 x Opteron > 2216, da3 is on a 3ware 9550-12 > > we are seeing this error: > g_vfs_done():da3s1a[READ(offset=81064794762854400, length=8192)]error = 5 > on a 12 GB Hyperdrive I trashed a perfectly disk drive before learning that there is a serious bug in g_vfs. Apparently it is one of those things which shows up in some configurations and not others. Although I am told they are unable to isolate the problem, all the reports I've seen were from people using AMD systems.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071014103129.W19754>