From owner-freebsd-fs@FreeBSD.ORG Sun Dec 14 15:47:29 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1F7E1065670; Sun, 14 Dec 2008 15:47:29 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by mx1.freebsd.org (Postfix) with ESMTP id 4B7A08FC21; Sun, 14 Dec 2008 15:47:29 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so942238yxb.13 for ; Sun, 14 Dec 2008 07:47:28 -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=5FFmonQ1Zuc0CjPKY3+ALKvpy2FVIzHg5DaZQOz3iSs=; b=E9WHhKL63uzEDX6KjpzB8nVkr7M0cgFMHNSUpUUHi0EIVs9W0OMF2dmDsmD87mURQQ ifQH0mKg0QIQtELnr/bj4EYZibbn5TpStm81sYgDsXv+Z0e0NE7ATz1i1JIxDR6ZMjjE IJgIbOoVFR8d3BMSCtpayyCBLAQzCnJuvVV5s= 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=Owibq86s8SiTwIA+N/StEzdDFLY0QIU0e1aMt0uuhkDAvwJ1U63ex+GmN5QD8rJ7vD W49NQpa7EBB80cL/Dx6wRtTKGtzcLBXVQIrAgpJXohBEYC226q8/FzD5HZP6f9Ij/QM+ hGiOrMtvqW9XAwdJ+LZOapkPANs1BWqSM2U/8= Received: by 10.231.18.130 with SMTP id w2mr68628iba.11.1229269648344; Sun, 14 Dec 2008 07:47:28 -0800 (PST) Received: by 10.231.11.72 with HTTP; Sun, 14 Dec 2008 07:47:28 -0800 (PST) Message-ID: <3a142e750812140747r2eb5ebadp7ac2b2c8ae357bae@mail.gmail.com> Date: Sun, 14 Dec 2008 16:47:28 +0100 From: "Paul B. Mahol" To: "Bruce M Simpson" In-Reply-To: <4944501E.40900@incunabulum.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8cb6106e0811241129o642dcf28re4ae177c8ccbaa25@mail.gmail.com> <8cb6106e0812031453j6dc2f2f4i374145823c084eaa@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> Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, "Bruce M. Simpson" Subject: Re: ext2fuse: user-space ext2 implementation X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Dec 2008 15:47:29 -0000 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. -- Paul