Date: Sun, 14 Oct 2007 18:13:26 -0600 From: Scott Long <scottl@samsco.org> To: Jan Mikkelsen <janm@transactionware.com> Cc: freebsd-stable@freebsd.org, 'Ivan Voras' <ivoras@freebsd.org>, freebsd-geom@freebsd.org Subject: Re: g_vfs_done():da3s1a[READ(offset=81064794762854400, length=8192)]error = 5 Message-ID: <4712B0A6.1050408@samsco.org> In-Reply-To: <000a01c80ebb$49227f90$db677eb0$@com> References: <008801c80e65$47cbe650$639049d9@EC1a> <feu58o$5uo$1@ger.gmane.org> <4712A494.30803@samsco.org> <000a01c80ebb$49227f90$db677eb0$@com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jan Mikkelsen wrote: > Scott Long wrote: >> Ivan Voras wrote: >>> 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. > > Well, perhaps not directly but I think filesystem corruption can > indirectly cause g_vfs_done messages. > > If a filesystem is corrupt, the filesystem might attempt to read an > out-of-range block, leading to a g_vfs_done error. This was the > case for some of the arcmsr problems last year. > > In this case, I think the original poster said that the block > number was out of range for the device. > > Regards, > > Jan Mikkelsen > > Yeah, you're right, the block number is absurd, and it could well be caused by a bad block pointer in the filesystem. It sounds like he's getting this problem even on fresh installs, which ordinarily would point to a bad driver. If it's happening with both TWA and ATA, it's hard to blame both of those drivers. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4712B0A6.1050408>