Subject: Re: Ideas on un-breaking an LFS partition?
To: None <email@example.com>
From: Scott Ellis <firstname.lastname@example.org>
Date: 11/15/2006 21:40:39
Scott Ellis wrote:
> Anyone have any recommendations on what to do to get my LFS un-broken (seek
> kern/35054)? It doesn't have data that I care about on it, but with all the
> talk lately about LFS being more-stable (and potentially even usable as /),
> I figure there must be some way other than fsck_lfs to recover data. For
> me, fsck_lfs doesn't seem to actually fix the filesystem.
> What other recourse would an admin have to repair the partition (short of
> re-newfs'ing it and restoring from a backup)?
So I newfs'ed the partition (this time using just "-A" with newfs_lfs,
rather than "-A -b 65536") and repeated the test. The pax command
seemed to work, but I get:
Nov 15 21:24:06 intrepid /netbsd: lfs_writeinode: looping count=3
Nov 15 21:24:06 intrepid /netbsd: lfs_writeinode: looping count=82
This is wrapped in an #ifdef DEBUG, but I'm not entirely clear if this
is an expected condition or not. Should I take this as a sign of
instability (or a potential problem), just just simple debug output?