From owner-freebsd-questions@FreeBSD.ORG Wed Dec 3 22:28:24 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2ED51065705 for ; Wed, 3 Dec 2008 22:28:24 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id 5B2D88FC17 for ; Wed, 3 Dec 2008 22:28:23 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1590855ywe.13 for ; Wed, 03 Dec 2008 14:28:23 -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=ZG57n6hPUdov84GG8dZO/C0ndB4nYtbAbCB24QqPCzI=; b=ZiZd9VRS57cjrazypaBnXzeU0FFXR7LJANuwBpAmtj3JatQ4kxu3/RKPWzO4tsHwmZ UG+TpKfaLc3XsGwoakkp2SGUOtLliVANRiGqEUqB/q+IdlfuUGCPy3ec+d1qtB917GHC 3/rlEJuFlFYTYVZyD7M4sEFf0m2GOTdbBVukE= 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=ovr7igABoG7999dQO1kaTs4rbx4P5Lx1SfHVbKkZqMGbzDSVeyzgIaYr4NAM4e1pvN iQuhat7i6nIVBwe11Hxn6Pdx8FYUNo+VoRX4PxuPAt6ZxsnCEoaQe+S6gIpOpZggeHAU ck5xzsZcKbnGVQukPza+hy/vooowrW9Tslu6A= Received: by 10.142.132.2 with SMTP id f2mr5601013wfd.6.1228343301998; Wed, 03 Dec 2008 14:28:21 -0800 (PST) Received: by 10.142.180.20 with HTTP; Wed, 3 Dec 2008 14:28:21 -0800 (PST) Message-ID: <1bd550a00812031428h158c1339u3568508964450bd9@mail.gmail.com> Date: Wed, 3 Dec 2008 23:28:21 +0100 From: "=?ISO-8859-1?Q?Fernando_Apestegu=EDa?=" To: josh.carroll@gmail.com In-Reply-To: <8cb6106e0812031401p45eb3f4di51b71e48d8819b@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1bd550a00812031145y7a94d7cbgf8c519ad35b2dce@mail.gmail.com> <8cb6106e0812031208k62c0979cjc97dd9fcdeb43b32@mail.gmail.com> <1bd550a00812031338o77f70007lbcc52325c91f5b3b@mail.gmail.com> <8cb6106e0812031401p45eb3f4di51b71e48d8819b@mail.gmail.com> Cc: FreeBSD Subject: Re: Mounting ext3fs partition X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2008 22:28:24 -0000 On Wed, Dec 3, 2008 at 11:01 PM, Josh Carroll wrote: >> Hi josh, >> >> Exactly, it is 256. So according to you, I can't use the mounted >> filesystem, right? >> >> Could you please explain in more detail, what the problem is? >> >> Thanks in advance. > > I believe around e2fsprogs version 1.40.5 or so, they changed the > default inode size from 128 to 256. The current ext2fs driver in > FreeBSD has a hard-coded inode size defined: > > #define EXT2_INODE_SIZE 128 > > I have a patch that dynamically determines this size, but I do not yet > have a good enough understanding of the ext2/3 spec to decide if the > changes I made are sufficient to fix the problem or if there is some > risk of breakage because the extra 128 is required for some metadata > of some sort. > > What happened in your case is something I was afraid of and what > prompted me to look into a fix in the first place - namely, newer > Linux distributions or even file systems created by e2fsprogs from > ports in FreeBSD will be unusable with the current ext2fs driver, > since it assumes a size of 128. > > There is some more information here regarding the patch and its current status: > > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2008-11/msg00421.html > > I (or even better, someone more knowledgeable about file systems) need > to read through the ext2/3 spec and determine if the changes I've made > cause any breakage. Ok, Thanks for the clarification and overall, thanks for the work of submitting the patch regardless of it is merged yet or not. > > Thanks, > Josh >