Date: Sun, 14 Oct 2007 17:21:56 -0600 From: Scott Long <scottl@samsco.org> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-stable@freebsd.org, freebsd-geom@freebsd.org Subject: Re: g_vfs_done():da3s1a[READ(offset=81064794762854400, length=8192)]error = 5 Message-ID: <4712A494.30803@samsco.org> In-Reply-To: <feu58o$5uo$1@ger.gmane.org> References: <008801c80e65$47cbe650$639049d9@EC1a> <feu58o$5uo$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Ivan Voras wrote: > 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 >> >> the offset changes sometimes, but it is always 81064794xxxxxxxxx and well >> out the 12GB range. > > Yes. > >> According to systat -vm, da3 does tps > 500 (yes, that's a lot) > > That's not a lot :) That's actually low for a modern solid state drive. > >> This leads to an assumption, the error has to do with very high IOs per >> second on a SMP machine. > > Either that or file system errors. Does fsck run ok or does it say > anything unusual? > No, filesystem corruption has nothing to do with g_vfs_done messages. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4712A494.30803>