From owner-freebsd-questions Fri Feb 4 12: 0:29 2000 Delivered-To: freebsd-questions@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by builder.freebsd.org (Postfix) with ESMTP id 981A4456E for ; Fri, 4 Feb 2000 11:36:09 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id MAA10293; Fri, 4 Feb 2000 12:24:07 -0600 (CST) (envelope-from dan) Date: Fri, 4 Feb 2000 12:24:07 -0600 From: Dan Nelson To: Konrad Heuer Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Softupdates & fsck Message-ID: <20000204122407.A8801@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from "Konrad Heuer" on Fri Feb 4 16:30:10 GMT 2000 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Feb 04), Konrad Heuer said: > I'd greatly be interested in experiences with softupdates turned on > for larger filesystems and recovery time after system crashes or > power failures. Is fsck really dispensable? If or if not, how long > does fsck take? Softupdates doesn't make fsck run any faster. It does make directory operations run as async speed, with no corruption problems in the event of a crash. Theoretically, a softupdates-mounted filesystem can be mounted 'dirty' and cleaned in the background, but I believe there are some problems with that that haven't been worked out yet. fsck time seems to be proportional to the number of files (so your CVS repo will really take along time :) On my machine, fsck'ing a 9-gig drive takes about 5 minutes. fsck'ing a 60-gig volume takes about 10 minutes, but there aren't very many files. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message