From owner-freebsd-stable@FreeBSD.ORG Fri May 16 15:35:34 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B39E11065670 for ; Fri, 16 May 2008 15:35:34 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from hpsmtp-eml11.kpnxchange.com (hpsmtp-eml11.kpnxchange.com [213.75.38.111]) by mx1.freebsd.org (Postfix) with ESMTP id 3F83D8FC21 for ; Fri, 16 May 2008 15:35:33 +0000 (UTC) (envelope-from willy@Offermans.Rompen.nl) Received: from cpsmtp-eml101.kpnxchange.com ([213.75.84.101]) by hpsmtp-eml11.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 May 2008 17:35:32 +0200 Received: from koko.offrom.nl ([86.82.183.148]) by cpsmtp-eml101.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 May 2008 17:35:31 +0200 Received: from wiz.vpn.offrom.nl (Debian-exim@wiz.vpn.offrom.nl [10.168.0.18]) by koko.offrom.nl (8.13.8/8.13.8) with ESMTP id m4GFZTjq083692; Fri, 16 May 2008 17:35:29 +0200 (CEST) (envelope-from willy@wiz.vpn.offrom.nl) Received: from willy by wiz.vpn.offrom.nl with local (Exim 4.63) (envelope-from ) id 1Jx20K-0002YR-2G; Fri, 16 May 2008 17:37:56 +0200 Date: Fri, 16 May 2008 17:37:56 +0200 From: Willy Offermans To: Jeremy Chadwick Message-ID: <20080516153755.GA9388@wiz.vpn.offrom.nl> References: <20080421190403.GA4625@wiz.vpn.offrom.nl> <20080421201047.GB6884@slackbox.xs4all.nl> <20080516121414.GD4618@wiz.vpn.offrom.nl> <20080516122759.GA61346@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080516122759.GA61346@eos.sc1.parodius.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV 0.92.1/7136/Fri May 16 14:56:53 2008 on koko.offrom.nl X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on koko.offrom.nl X-OriginalArrivalTime: 16 May 2008 15:35:32.0083 (UTC) FILETIME=[79F8E430:01C8B76A] Cc: freebsd-stable@FreeBSD.org Subject: Re: g_vfs_done error third part--PLEASE HELP! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Willy@Offermans.Rompen.nl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2008 15:35:34 -0000 Hello Jeremy and FreeBSD friends, On Fri, May 16, 2008 at 05:27:59AM -0700, Jeremy Chadwick wrote: > On Fri, May 16, 2008 at 02:14:14PM +0200, Willy Offermans wrote: > > On Mon, Apr 21, 2008 at 10:10:47PM +0200, Roland Smith wrote: > > > Did you notice any file corruption in the filesystem on ar0s1g? > > > > No the two disks are brand new and I did not encounter any noticeable > > file corruption. However I assume that nowadays bad sectors on HD are > > handled by the hardware and do not need any user interaction to correct > > this. But maybe I'm totally wrong. > > You're right, but it depends on the type of disk. SCSI disks will > report bad blocks to the OS regardless if it is about to mark the block > as a grown defect or not. PATA and SATA disks, on the other hand, will > report bad blocks to the OS only if the internal bad block list (which > it manages itself -- this is what you're thinking of) is full. > > There are still many conditions where PATA and SATA disks can induce > errors in the OS. If the disk is attempting to work around a bad block, > and there's a physical error (servo problem, head crash, repetitive > re-reads of the block due to dust, whatever -- something that "ties up" > the disk for long periods of time), ATA subsystem timeouts may be seen, > DMA errors, or whatever else. SMART stats will show this kind of > problem. > > > > Unmount the filesystem and run fsck(8) on it. Does it report any errors? > > > > sun# fsck /dev/ar0s1g > > ** /dev/ar0s1g > > ** Last Mounted on /share > > ** Phase 1 - Check Blocks and Sizes > > INCORRECT BLOCK COUNT I=34788357 (272 should be 264) > > CORRECT? [yn] y > > > > INCORRECT BLOCK COUNT I=34789217 (296 should be 288) > > CORRECT? [yn] y > > > > ** Phase 2 - Check Pathnames > > ** Phase 3 - Check Connectivity > > ** Phase 4 - Check Reference Counts > > ** Phase 5 - Check Cyl groups > > FREE BLK COUNT(S) WRONG IN SUPERBLK > > SALVAGE? [yn] y > > > > SUMMARY INFORMATION BAD > > SALVAGE? [yn] y > > > > BLK(S) MISSING IN BIT MAPS > > SALVAGE? [yn] y > > > > 182863 files, 17282440 used, 120206472 free (12448 frags, 15024253 > > blocks, 0.0% fragmentation) > > > > ***** FILE SYSTEM MARKED CLEAN ***** > > > > ***** FILE SYSTEM WAS MODIFIED ***** > > > > The usual stuff I would say. > > How is this usual?. It appears to me you did have some filesystem > corruption. > What kind of filesystem corruption and how to solve that? I see these messages frequently if a FreeBSD machine unexpectedly reboots. Not only on this system but also on others. I never worried about it. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, De jrus wah, Willy ************************************* W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 653 27 16 23 e-mail: Willy@Offermans.Rompen.nl Powered by .... (__) \\\'',) \/ \ ^ .\._/_) www.FreeBSD.org