Date: 08 Jul 2002 15:50:45 +0200 From: "Georg-W. Koltermann" <Georg.Koltermann@mscsoftware.com> To: Peter Wemm <peter@wemm.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: fsck hosed? Message-ID: <1026136245.61276.58.camel@hunter.muc.macsch.com> In-Reply-To: <20020708044114.22412380A@overcee.wemm.org> References: <20020708044114.22412380A@overcee.wemm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes, I see that as well. Another symptom is that fsck -p now always announces "unexpected inconsistencies" and drops back to singleuser when it indeed was able to fix the problems, i.e. it marks the filesystem clean and a manual fsck does not report anything unusual. My last cvsup was with date=2002.06.27.22.00.00 (pre-KSE III, post-UFS2). -- Regards, Georg. Am Mo, 2002-07-08 um 06.41 schrieb Peter Wemm: > It seems to be aborting the 'process all file systems' loop when it modifies > a file system. eg: 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?1026136245.61276.58.camel>