From owner-freebsd-questions Tue Apr 20 13: 3:17 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id CF1DA14EDB for ; Tue, 20 Apr 1999 13:03:14 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id NAA08414; Tue, 20 Apr 1999 13:00:45 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 20 Apr 1999 13:00:44 -0700 (PDT) From: Doug White To: Mohit Aron Cc: freebsd-questions@FreeBSD.ORG Subject: Re: fragmentation reports on clean reboots In-Reply-To: <199904162039.PAA22462@cs.rice.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 16 Apr 1999, Mohit Aron wrote: > Hi, > I'm using FreeBSD-2.2.6 and whenever I reboot my machine, I see reports > of disk fragmentation and the machine spends 5 seconds or so fixing the > problem. This happens even when the previous reboot was a clean one (no > kernel crashes). (Of course if there's an OS crash, the filesystem needs a > longer time to fix upon a reboot.) Can someone tell me why FreeBSD reports > filesystem defects even when previous shutdown was a clean one ? I think > the problem also exists on FreeBSD-3.x (someone told me) though I haven't > had first-hand experience with that. Could you post the message you're seeing? Fragments are normal. As long as it says 'FILESYSTEM CLEAN' then you're shutting down correctly. Another sign of a bad shutdown will be the kernel message WARNING: / was not dismounted properly. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message