Date: Wed, 20 Mar 2002 03:46:12 -0800 From: "Crist J. Clark" <crist.clark@attbi.com> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: current@FreeBSD.ORG Subject: Re: "Unexpected Soft Update Inconsistency" Message-ID: <20020320034612.I67739@blossom.cjclark.org> In-Reply-To: <3044.1016605252@critter.freebsd.dk>; from phk@critter.freebsd.dk on Wed, Mar 20, 2002 at 07:20:52AM %2B0100 References: <20020319220118.F67739@blossom.cjclark.org> <3044.1016605252@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 20, 2002 at 07:20:52AM +0100, Poul-Henning Kamp wrote: > > Sounds like your disklabel is smaller than your filesystem ? Huh. That's what it looks like. "How'd that happen?"(tm) I don't recall ever touching the disklabel since the install. Oh, well. There was enough spare room on the disk to do a bare-bones OS install on an open slice, backed up the bad filesystem and the others on the slice, repartitioned the slice a little better now that I have a feel for how the system will be used, newfs'ed all of the partitions, and restored. > In message <20020319220118.F67739@blossom.cjclark.org>, "Crist J. Clark" writes > : > >I've got a -CURRENT system that is seriously resisting attempts to > >revive it. No matter how many times I run fsck(8), it tells me, > > > >** /dev/ad0s1a > >** Last Mounted on / > >** Root file system > >** Phase 1 - Check Blocks and Sizes > > > >CANNOT READ BLK: 8407744 > >UNEXPECTED SOFT UPDATE INCONSISTENCY > > > >CONTINUE? yes > > > >THE FOLLOWING DISK SECTORS COULD NOT BE READ: 8407744, 8407745, 8407746, 8407747, 8407748, 8407749, 8407750, 8407751, 8407752, 8407753, 8407754, 8407755, 8407756, 8407757, 8407758, 8407759, > >** Phase 2 - Check Pathnames > >** Phase 3 - Check Connectivity > >** Phase 4 - Check Reference Counts > >** Phase 5 - Check Cyl groups > >133720 files, 1429523 used, 2651122 free (34074 frags, 327131 blocks, 0.8% fragmentation) > > > >***** FILE SYSTEM STILL DIRTY ***** > > > >***** PLEASE RERUN FSCK ***** > > > >There are no reports of hard errors, so I believe this is purely a > >"soft" error. Any advice on how to fix? > >-- > >Crist J. Clark | cjclark@alum.mit.edu > > | cjclark@jhu.edu > >http://people.freebsd.org/~cjc/ | cjc@freebsd.org > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-current" in the body of the message > > > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020320034612.I67739>