From owner-freebsd-current Wed Nov 21 7:35:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from leviathan.inethouston.net (leviathan.inethouston.net [66.64.12.249]) by hub.freebsd.org (Postfix) with ESMTP id 32AA837B416 for ; Wed, 21 Nov 2001 07:35:22 -0800 (PST) Received: by leviathan.inethouston.net (Postfix, from userid 1001) id 108CE10F43E; Wed, 21 Nov 2001 09:35:19 -0600 (CST) Date: Wed, 21 Nov 2001 09:35:19 -0600 From: "David W. Chapman Jr." To: Mikhail Teterin Cc: current@freebsd.org Subject: Re: damaged file system despite unmounts Message-ID: <20011121153518.GB91521@leviathan.inethouston.net> Reply-To: "David W. Chapman Jr." Mail-Followup-To: Mikhail Teterin , current@freebsd.org References: <200111211417.fALEHEO60866@aldan.algebra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200111211417.fALEHEO60866@aldan.algebra.com> User-Agent: Mutt/1.3.23.2i X-Operating-System: FreeBSD 4.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Nov 21, 2001 at 09:17:13AM -0500, Mikhail Teterin wrote: > For a while I was noticing my largest FS reported as not unmounted > cleanly on boot. Today I decided to unmount it myself and check it with > fsck. Here are the results. Notice, that the first fsck had to mark the > FS clean. Notice that the second fsck found something else to do, and > only the third one was happy. What's happening? Thanks, > > -mi > I noticed this a while ago on -current. I haven't checked recently, but I do remember having this problem -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. dwcjr@freebsd.org FreeBSD Committer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message