Date: Mon, 19 Oct 1998 00:31:52 -0600 From: Warner Losh <imp@village.org> To: Don Lewis <Don.Lewis@tsc.tdk.com> Cc: Nate Williams <nate@mt.sri.com>, Terry Lambert <tlambert@primenet.com>, hackers@FreeBSD.ORG Subject: Re: softupdates and/or fsck bugs or features? Message-ID: <199810190631.AAA19911@harmony.village.org> In-Reply-To: Your message of "Sun, 18 Oct 1998 14:15:07 PDT." <199810182115.OAA29673@salsa.gv.tsc.tdk.com> References: <199810182115.OAA29673@salsa.gv.tsc.tdk.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199810182115.OAA29673@salsa.gv.tsc.tdk.com> Don Lewis writes: : Question for Warner, do you see any complaints from fsck about : extraneous hard links to directories? After fsck has run, I've : seen another fsck run complain that /lost+found/#whatever is an : extraneous hard link to a directory. No. Didn't see those messages. : In the meantime, I'd recommend running fsck until it stops reconnecting : stuff under lost+found. Then run it again without the -p option (so that : it ignores the clean flag), which will allow it to fix the reference : counts. That's what I wound up doing, with some scrubbing of lost+found inbetween runs, to get back to a fsck that was clean. I think what was happening was that the link count was adjusted for files that were dangling because fsck couldn't attach them to lost+found because the directory was full. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810190631.AAA19911>