From owner-freebsd-current Mon Mar 17 19:51: 0 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E391237B401; Mon, 17 Mar 2003 19:50:58 -0800 (PST) Received: from bluejay.mail.pas.earthlink.net (bluejay.mail.pas.earthlink.net [207.217.120.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 277A243F93; Mon, 17 Mar 2003 19:50:58 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0217.cvx22-bradley.dialup.earthlink.net ([209.179.198.217] helo=mindspring.com) by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18v87h-0001xJ-00; Mon, 17 Mar 2003 19:50:46 -0800 Message-ID: <3E769745.FA122633@mindspring.com> Date: Mon, 17 Mar 2003 19:49:25 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bakul Shah Cc: Poul-Henning Kamp , Julian Elischer , FreeBSD current users , fs@FreeBSD.ORG Subject: Re: Anyone working on fsck? References: <200303172205.RAA18117@goliath.cnchost.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a43f68e6a0fb7949f13380241dbafb9eb7350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c 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 Bakul Shah wrote: > > I have been tending UNIX computers of all sorts for many years and > > there is one bit of wisdom that has yet to fail me: > > > > Every now and then, boot in single-user and run full fsck > > on all filesystems. > > > > If this had failed to be productive, I would have given up the > > habit years ago, but it is still a good idea it seems. > > Even now I use fsck in forground since the background fsck > was not stable enough the last time I used it. But I > remember thinking fsck was taking too long for as long as I > have used it (since 1981). If your problem is "availability", then any "time > 0" counts as "too long". Taking the whole system offline, while the rest of the world has gone into an electronic transaction frenzy because some world event, and running a BG fsck is not really an option. > Anything that runs for half hour or more in fg is likely to > take longer in bg. What happens if the system crashes again > before it finishes? Will bg fsck handle that? Am I right in > thinking that it can not save files in /lost+found? It can, but it has to be changed; it's pretty ugly. Your best bet is to precreate "lost+found", and then modify the code to allow you to ftruncate(2) a directory large, forcibly allocating backing blocks for it (that was my last workaround to the problem). > > Optimizing fsck is a valid project, I just wish it would be somebody > > who would also finish the last 30% who would do it. > > I am skeptical you will get more than a factor of 2 > improvement without changing the FS (but hey, that is 3 hours > for Julian so I am sure he will be happy with that!). I'm skeptical you will get a factor of 2. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message