Date: Thu, 24 Dec 2009 15:19:16 -0800 (PST) From: Dan Strick <mla_strick@att.net> To: FreeBSD-gnats-submit@FreeBSD.org Cc: mla@mist.nodomain Subject: misc/141992: fsck cannot repair file system in which it finds an error Message-ID: <200912242319.nBONJFjB020259@mist.nodomain> Resent-Message-ID: <200912242320.nBONK2Gk048165@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 141992 >Category: misc >Synopsis: fsck cannot repair file system in which it finds an error >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Dec 24 23:20:02 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Dan Strick <mla_strick@att.net> >Release: FreeBSD 8.0-RELEASE i386 >Organization: none >Environment: System: FreeBSD mist 8.0-RELEASE FreeBSD 8.0-RELEASE #5: Mon Dec 7 18:59:52 PST 2009 root@mist:/usr/src/sys/i386/compile/MIST_DEBUG i386 >Description: When I upgraded from FreeBSD release 6.1 to release 8.0 I discovered that fsck complained about a problem in one of my old file systems and claimed to have fixed the problem but did not really fix it. The fsck on release 6.1 finds no problem at all in the file system. I wonder if perhaps fsck could not fix the problem because there was no real problem and fsck was confused by some difference in file systems created by an older release of FreeBSD. >How-To-Repeat: This is a sample fsck dialogue under FreeBSD release 8.0. I do not claim that the file system meets all release 8.0 standards for UFS file systems (since it was created under an old FreeBSD release) but I do claim that it is a bug for fsck to have claimed to have fixed a problem and then to find the problem again when the fsck is repeated. mist# fsck /dev/ad4s4a ** /dev/ad4s4a ** Last Mounted on /fs/u4 ** Phase 1 - Check Blocks and Sizes CYLINDER GROUP 48: BAD MAGIC NUMBER UNEXPECTED SOFT UPDATE INCONSISTENCY REBUILD CYLINDER GROUP? [yn] y ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups SUMMARY INFORMATION BAD SALVAGE? [yn] y BLK(S) MISSING IN BIT MAPS SALVAGE? [yn] y 46090 files, 2542520 used, 1766975 free (22607 frags, 218046 blocks, 0.5% fragmentation) ***** FILE SYSTEM IS CLEAN ***** ***** FILE SYSTEM WAS MODIFIED ***** mist# !! fsck /dev/ad4s4a ** /dev/ad4s4a ** Last Mounted on /fs/u4 ** Phase 1 - Check Blocks and Sizes CYLINDER GROUP 48: BAD MAGIC NUMBER UNEXPECTED SOFT UPDATE INCONSISTENCY REBUILD CYLINDER GROUP? [yn] y ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups SUMMARY INFORMATION BAD SALVAGE? [yn] y BLK(S) MISSING IN BIT MAPS SALVAGE? [yn] y 46090 files, 2542520 used, 1766975 free (22607 frags, 218046 blocks, 0.5% fragmentation) ***** FILE SYSTEM IS CLEAN ***** ***** FILE SYSTEM WAS MODIFIED ***** mist# >Fix: (workaround:) 1) Dump the file system. 2) Newfs the file system under FreeBSD release 8.0. 3) Restore the file system. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200912242319.nBONJFjB020259>