From owner-freebsd-stable@FreeBSD.ORG Fri Dec 19 21:51:57 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 211881065670 for ; Fri, 19 Dec 2008 21:51:57 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242]) by mx1.freebsd.org (Postfix) with ESMTP id 8FF7E8FC14 for ; Fri, 19 Dec 2008 21:51:56 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: by an-out-0708.google.com with SMTP id c2so702747anc.13 for ; Fri, 19 Dec 2008 13:51:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=CbFMCaXSnqCyQsMJFg75av8iS/VfrRdzfoCF5WpVPzg=; b=Wuy3add+RzKKcEWelBZc2U7jokIZ+L3xsBttQTruD6Qg8k4xsXUUeHC0fRNyOLxdqd ZCh6GBEJfp4RLnSJ7UHjMjhquYNu1Cs6we5g3J1KRhDiP/lFYwE+oIKOPHGR95hB+sY6 3bR5rhgqsd3G+MC2DtKQOXSaap9422So1DxzU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=IF+JLheD6QD7ktu81lulkaBLIo9B3LQpXT3ETxhuV56aCeTeXZLrM6MHWwaQlzPT02 oLvacQ3xs67EaOwJN+EeVX0FtuPlfhF37s8L6Xw62UxD5mzj/B0NGP6LSi3KkhK0JGnO bnBmyVAVp/A8QGjf/uke4u0PTmjdPnDrXHi5g= Received: by 10.100.128.2 with SMTP id a2mr2526692and.158.1229723514081; Fri, 19 Dec 2008 13:51:54 -0800 (PST) Received: by 10.100.4.14 with HTTP; Fri, 19 Dec 2008 13:51:54 -0800 (PST) Message-ID: <539c60b90812191351i6090f24ejb9006471f74f01b9@mail.gmail.com> Date: Fri, 19 Dec 2008 14:51:54 -0700 From: "Steve Franks" To: "Paul B. Mahol" In-Reply-To: <3a142e750812140747r2eb5ebadp7ac2b2c8ae357bae@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <200812041747.09040.gnemmi@gmail.com> <4938FE44.9090608@FreeBSD.org> <4939133E.2000701@FreeBSD.org> <493CEE90.7050104@FreeBSD.org> <3a142e750812090553l564bff84pe1f02cd1b03090ff@mail.gmail.com> <4943F43B.4060105@incunabulum.net> <3a142e750812131403p31841403ub9d5693278c74111@mail.gmail.com> <4944501E.40900@incunabulum.net> <3a142e750812140747r2eb5ebadp7ac2b2c8ae357bae@mail.gmail.com> Cc: freebsd-fs@freebsd.org, "Bruce M. Simpson" , Bruce M Simpson , freebsd-stable@freebsd.org Subject: Re: ext2fuse: user-space ext2 implementation X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Dec 2008 21:51:57 -0000 On Sun, Dec 14, 2008 at 8:47 AM, Paul B. Mahol wrote: > On 12/14/08, Bruce M Simpson wrote: >> Paul B. Mahol wrote: >>>> Can you please relay this feedback to the authors of ext2fuse? >>>> >>>> As mentioned earlier in the thread, the ext2fuse code could benefit from >>>> UBLIO-ization. Are you or any other volunteers happy to help out here? >>>> >>> >>> Well, first higher priority would be to fix existing bugs. It would be >>> very little >>> gain with user cache, because it is already too much IMHO slow and >>> adding user cache >>> will not make it faster, but that is not port problem. >>> >> >> I'm not aware of bugs with ext2fuse itself; my work on the port was >> merely to try to raise awareness that a user-space project for ext2 >> filesystem access existed. >> >> Can you elaborate further on your experience with ext2fuse which seems >> to you to be buggy, i.e. symptoms, root cause analysis etc. ? Have you >> reported these to the author(s)? > > I have read TODO. > >> Have you measured the performance? Is the performance sufficient for the >> needs of an occasional desktop user? > > Performance was not sufficient, and adding user cache will not improve access > speed on first read. > After mounting ext2fs volume (via md(4)) created with e2fsprogs port > and copying data > from ufs to ext2, reading was quite slow. Also ext2fuse after mount > doesnt exits it > is still running displaying debug data - explaining why project > itselfs is in alpha > state. > >> I realise we are largely involved in content-free argument here, however >> the trade-off of ext2fuse vs ext2fs in the FreeBSD kernel source tree, >> is that of a hopefully more actively maintained implementation vs one >> which is not maintained at all, and any alternatives for FreeBSD users >> would be welcome. > > Project itself doesnt look very active, but I may be wrong. It is in alpha state > as reported on SF. > IMHO it is better to maintain our own because it is in better shape, but I'm not > intersted in ext* as developer. AFAIK our ext* either barfs or corrupts ext3, and since linux is pretty much all using ext3 these days, we're stuck in read-only for ext3, which is rather undesirable, methinks (seems everyone's using fuse's ntfs for this same reason [which is stable, however]). Which is not to say stealing the ext3 (journal?) implementation and putting it in our code isn't a better choice, I'm just pointing out there is no good choice right now... Steve