From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 19:48:56 2004 Return-Path: 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 9D5E016A4CE for ; Thu, 2 Dec 2004 19:48:56 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1432F43D5C for ; Thu, 2 Dec 2004 19:48:56 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so838439rnf for ; Thu, 02 Dec 2004 11:48:55 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=Ki61+4bGgZTa+pxGuHQg7t5soSheBRucbCjxs+R05dXE+VGueJiek9LQdVa0vCwZXKVujPv/YWk0D25471VUqZrPAWFON8yVbmq3HFnoBiEIflCy7ZHF3UA4ZiQVxm/WDen3OV89WJeSxCLDHLOOIfPGK0XegByYKs/0z8vgzjM= Received: by 10.38.96.9 with SMTP id t9mr148987rnb; Thu, 02 Dec 2004 11:48:54 -0800 (PST) Received: by 10.38.15.38 with HTTP; Thu, 2 Dec 2004 11:48:54 -0800 (PST) Message-ID: Date: Thu, 2 Dec 2004 19:48:54 +0000 From: Eric Kjeldergaard To: Scott Long In-Reply-To: <41AE3F80.1000506@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41AE3F80.1000506@freebsd.org> cc: hackers@freebsd.org cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Eric Kjeldergaard List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 19:48:56 -0000 > 4. Journaled filesystem. While we can debate the merits of speed and > data integrety of journalling vs. softupdates, the simple fact remains > that softupdates still requires a fsck run on recovery, and the > multi-terabyte filesystems that are possible these days make fsck a very > long and unpleasant experience, even with bg-fsck. There was work at > some point at RPI to add journaling to UFS, but there hasn't been much > status on that in a long time. There have also been proposals and > works-in-progress to port JFS, ReiserFS, and XFS. Some of these efforts > are still alive, but they need to be seen through to completion. But at > the risk of opening a can of worms here, I'll say that it's also > important to explore non-GPL alternatives. A thread (http://lists.freebsd.org/pipermail/freebsd-current/2004-October/040904.html )happens to be talking about ro support for the ReiserFS. After having used this for quite some time in a Linux environment, I can't help but notice that it seriously outperforms any other filesystem I've tried on large numbers of littlish files. A beautiful application that I've rather wanted to try for a while was this on the ports tree. The stage of the current implementation is, as I said, read-only. Further, it's currently i386 only. However, I think that there is enough interest in this new (and relatively exciting) filesystem that we may be able to find some developers with time (Possibly including myself) and desire to try to implement write support and do some porting. To ease any qualms with regards to licensing, it appears (http://lists.freebsd.org/pipermail/freebsd-current/2004-October/040998.html) that the current implementation is BSD licensed. -- If I write a signature, my emails will appear more personalised.