From owner-freebsd-fs@FreeBSD.ORG Mon Apr 4 16:55:27 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E70F9106564A for ; Mon, 4 Apr 2011 16:55:26 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by mx1.freebsd.org (Postfix) with ESMTP id 933278FC12 for ; Mon, 4 Apr 2011 16:55:26 +0000 (UTC) Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19]) by qmta05.westchester.pa.mail.comcast.net with comcast id TTjf1g0080QuhwU55UvSpn; Mon, 04 Apr 2011 16:55:26 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta02.westchester.pa.mail.comcast.net with comcast id TUvN1g01X1t3BNj3NUvPk8; Mon, 04 Apr 2011 16:55:26 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 5959E9B429; Mon, 4 Apr 2011 09:55:21 -0700 (PDT) Date: Mon, 4 Apr 2011 09:55:21 -0700 From: Jeremy Chadwick To: binto Message-ID: <20110404165521.GA59495@icarus.home.lan> References: <00c101cbf2bf$4b03b2c0$140124c0@DBLJSW1S> <4D99DE50.1030607@bellanet.org> <00f201cbf2d7$29816f30$140124c0@DBLJSW1S> <011901cbf2da$672f0c40$140124c0@DBLJSW1S> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <011901cbf2da$672f0c40$140124c0@DBLJSW1S> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2011 16:55:27 -0000 On Mon, Apr 04, 2011 at 11:10:14PM +0800, binto wrote: > suspicious one is..bad sector.. > > ----- Original Message ----- From: "binto" > To: "Graham Todd" ; > Sent: Monday, April 04, 2011 10:47 PM > Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? > > > >if cabling, i wonder why in single mode there's no problem > >especially about filesystem . > >But in normal login when i use root user, then i got so many warn > >about that error 6. > >reboot after that. > >??? [ can u explain?] > > > >now i'm still troubleshoot in configuration. > >i haven't try run hardware test yet. such as to switch HDD with > >another board or something. > > > >so far i haven't found missing data, except files that i remove..:D > > > >thanks > > > >----- Original Message ----- From: "Graham Todd" > > > >To: "binto" ; > >Sent: Monday, April 04, 2011 11:05 PM > >Subject: Re: what is g_vfs_done() and error = 6?? how to fix it?? > > > > > >>On 04/04/2011 07:56, binto wrote: > >>>Also i got before it's reboot suddenly: > >>>panic: initiate_write_inodeblock_ufs2: already started > >> > >>I think you're getting a panic from ufs2 and softdep somewhere > >>because for whatever reason geom is saying the drive has > >>disappeared (bad cabling, bad hardware, bad sector, electrical > >>glitch, etc.)? Someone more knowledgeable than me can explain > >>the code path and error 6. > >> > >>If it is hardware and the drive that has your / or /usr > >>filesystems then panic'ing is "correct" behaviour I believe. If > >>it is a USB drive being pulled without umounting then I think > >>FreeBSD is supposed to handle that incorrect operation more > >>gracefully since 7.* > >> > >>Was there data loss? Did the server reboot properly? Have you > >>run any hardware tests? > >> > >>cheers > >> > >>>Thanks > >>>Binto > >>> ----- Original Message ----- > >>> From: binto > >>> To: freebsd-fs@freebsd.org > >>> Sent: Monday, April 04, 2011 7:39 PM > >>> Subject: what is g_vfs_done() and error = 6?? how to fix it?? > >>> > >>> > >>> I got error message& my server suddenly drop : > >>> > >>> g_vfs_done() error = 6 > >>> > >>> g_vfs_done(): ad10s2a[READ(offset=1348599808, > >>>length=16384)]error = 6 anyone can help me please?? > >>> > >>> Thank you > >>> binto Install /usr/ports/sysutils/smartmontools and provide output from "smartctl -a /dev/ad10" (assuming the questionable hard disk is still installed there); I can help decode the output. You might also want to run "fsck -f /dev/ad10". There are known cases where backgrounded fsck can't fix some errors, but I'm not sure if the kernel would return errno=6 (Device not configured) to userland in this situation. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB |