From owner-freebsd-current@FreeBSD.ORG Sat Jan 9 01:39:55 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA6C0106566C; Sat, 9 Jan 2010 01:39:55 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.210.172]) by mx1.freebsd.org (Postfix) with ESMTP id 9A4848FC08; Sat, 9 Jan 2010 01:39:55 +0000 (UTC) Received: by yxe2 with SMTP id 2so5097974yxe.7 for ; Fri, 08 Jan 2010 17:39:52 -0800 (PST) Received: by 10.91.182.8 with SMTP id j8mr2747148agp.48.1263001191014; Fri, 08 Jan 2010 17:39:51 -0800 (PST) Received: from ?10.0.1.198? (udp022762uds.hawaiiantel.net [72.234.79.107]) by mx.google.com with ESMTPS id 22sm8173648ywh.45.2010.01.08.17.39.49 (version=SSLv3 cipher=RC4-MD5); Fri, 08 Jan 2010 17:39:50 -0800 (PST) Date: Fri, 8 Jan 2010 15:42:35 -1000 (HST) From: Jeff Roberson X-X-Sender: jroberson@desktop To: Ivan Voras In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Help test softupdates journaling (SUJ) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jan 2010 01:39:56 -0000 On Sat, 9 Jan 2010, Ivan Voras wrote: > Jeff Roberson wrote: >> Hello, >> >> I have been augmenting softupdates with a small journal that will be >> processed in lieu of fsck in the event of a crash. I have written some >> about this project here: http://jeffr_tech.livejournal.com/ > > Good news! > >> For now I need volunteers who will attempt to crash the kernel code. It >> now passes fsx, fsstress, and stress2 on my box for many hours. pho@ has >> been helping me and may still have a bug or two but I need a wider audience >> so we can be comfortable with the stability. In a week or so I will also >> provide the checker. Until then a full fsck is required after a crash. > > Hi, > > Do you mean that journal replay/recovery is implemented but not 100% working > yet so a fsck is needed or that it is still missing? Hi Ivan, It is implemented. You can search for suj.c in the patch if you would like to review the source. It is part of fsck_ffs. Currently it does not have perfect information from the kernel in some cases. I'm working on fixing those now, and I believe I know what all of them are. For the next step in testing I will ask volunteers to run the suj recovery stage followed by a full filesystem check. If the full check turns up any problems we will know the recovery stage is not yet perfect. The recovery code produces a text log when the -d flag is supplied which produces about 10MB of text for every 1MB of journal but tells me exactly what happened as diagnosing these problems can be quite difficult. I also need to work on performance some although it tends to take only a couple of seconds for each valid megabyte in the journal. I suspect the final maximum journal size will be around 32MB which would limit fsck to around a minute in the worst case of 1 million valid journal records. Thanks, Jeff > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >