From owner-freebsd-stable@FreeBSD.ORG Fri May 16 19:07:20 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 AB4591065670 for ; Fri, 16 May 2008 19:07:20 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from smtp-vbr10.xs4all.nl (smtp-vbr10.xs4all.nl [194.109.24.30]) by mx1.freebsd.org (Postfix) with ESMTP id 3D2CB8FC13 for ; Fri, 16 May 2008 19:07:20 +0000 (UTC) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr10.xs4all.nl (8.13.8/8.13.8) with ESMTP id m4GJ7I60075427; Fri, 16 May 2008 21:07:19 +0200 (CEST) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 2FF0BB82A; Fri, 16 May 2008 21:07:18 +0200 (CEST) Date: Fri, 16 May 2008 21:07:18 +0200 From: Roland Smith To: Willy Offermans Message-ID: <20080516190718.GA73178@slackbox.xs4all.nl> Mail-Followup-To: Willy Offermans , freebsd-stable@freebsd.org References: <20080421190403.GA4625@wiz.vpn.offrom.nl> <20080421201047.GB6884@slackbox.xs4all.nl> <20080516121414.GD4618@wiz.vpn.offrom.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline In-Reply-To: <20080516121414.GD4618@wiz.vpn.offrom.nl> X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 X-GPG-Key: http://www.xs4all.nl/~rsmith/pubkey.txt X-GPG-Notice: If this message is not signed, don't assume I sent it! User-Agent: Mutt/1.5.17 (2007-11-01) X-Virus-Scanned: by XS4ALL Virus Scanner 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 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 19:07:20 -0000 --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 16, 2008 at 02:14:14PM +0200, Willy Offermans wrote: > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/ar0s1a 20308398 230438 18453290 1% / > devfs 1 1 0 100% /dev > /dev/ar0s1d 21321454 3814482 15801256 19% /usr > /dev/ar0s1e 50777034 5331686 41383186 11% /var > /dev/ar0s1f 101554150 18813760 74616058 20% /home > /dev/ar0s1g 274977824 34564876 218414724 14% /share >=20 > pretty normal I would say. Yes. > > Did you notice any file corruption in the filesystem on ar0s1g? >=20 > 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. Every ATA disk has spare sectors, and they usually don't report bad blocks untill the spares are exhausted. In which case it is prudent to replace the disk. > > Unmount the filesystem and run fsck(8) on it. Does it report any errors? >=20 > sun# fsck /dev/ar0s1g=20 > ** /dev/ar0s1g > ** Last Mounted on /share > ** Phase 1 - Check Blocks and Sizes > INCORRECT BLOCK COUNT I=3D34788357 (272 should be 264) > CORRECT? [yn] y >=20 > INCORRECT BLOCK COUNT I=3D34789217 (296 should be 288) > CORRECT? [yn] y >=20 > ** 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 >=20 > SUMMARY INFORMATION BAD > SALVAGE? [yn] y >=20 > BLK(S) MISSING IN BIT MAPS > SALVAGE? [yn] y >=20 > 182863 files, 17282440 used, 120206472 free (12448 frags, 15024253 > blocks, 0.0% fragmentation) >=20 > ***** FILE SYSTEM MARKED CLEAN ***** >=20 > ***** FILE SYSTEM WAS MODIFIED ***** >=20 > The usual stuff I would say. Disk corruption is never normal. It can be explained by if the machine crashed or was power-cycles before the disks were unmounted, but it can also indicate hardware troubles. > > > Any hints are very much appreciated. > So I have to conclude that the write error message does make sense and > that something seems to be wrong with the disks. The next question is > what can I do about it? Should I return the disks to the shop and ask > for new ones? Install sysutils/smartmontools, and run 'smartctl -A /dev/adX|less', where X are the numbers of the drives in the RAID array. In the output, look at the values for Reallocated_Sector_Ct, Current_Pending_Sector, Offline_Uncorrectable, which is the last number that you see on each line. A small number for Reallocated_Sector_Ct is allowable. But non-zero counts for Current_Pending_Sector or Offline_Uncorrectable means it's time to get a new disk. > However other people that I have contacted and who had a similar > problem before have solved it by using software raid setup instead of a > hardware raid setup. This seems to indicate that there is some bug in > the FreeBSD code. The RAID support that you find on most desktop motherboards _is_ software RAID. See ataraid(4). Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkgt22UACgkQEnfvsMMhpyVvxACdElN6UcWmej8KV+H2iZZgUrhK z1cAoIQh+c5yptPN58KAPhVlGVTw4exp =Eeol -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK--