From owner-freebsd-questions Fri Apr 16 13:41:47 1999 Delivered-To: freebsd-questions@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 6A6C8159C7 for ; Fri, 16 Apr 1999 13:41:45 -0700 (PDT) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id PAA22462 for freebsd-questions@freebsd.org; Fri, 16 Apr 1999 15:39:22 -0500 (CDT) From: Mohit Aron Message-Id: <199904162039.PAA22462@cs.rice.edu> Subject: fragmentation reports on clean reboots To: freebsd-questions@freebsd.org Date: Fri, 16 Apr 1999 15:39:21 -0500 (CDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message