From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 7 15:21:53 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C5E51065676 for ; Sun, 7 Sep 2008 15:21:53 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.60.158]) by mx1.freebsd.org (Postfix) with ESMTP id 193758FC14 for ; Sun, 7 Sep 2008 15:21:53 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: by syn.atarininja.org (Postfix, from userid 1001) id 627AD5C5B; Sun, 7 Sep 2008 11:07:47 -0400 (EDT) Date: Sun, 7 Sep 2008 11:07:47 -0400 From: Wesley Shields To: jT Message-ID: <20080907150747.GB62357@atarininja.org> References: <9f8af95f0809061626q22bc8f60i48fd95b32cef3d04@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9f8af95f0809061626q22bc8f60i48fd95b32cef3d04@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-hackers Subject: Re: 256-byte inode support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Sep 2008 15:21:53 -0000 On Sat, Sep 06, 2008 at 07:26:27PM -0400, jT wrote: > hackers, > > since tytso had updated ext3 -- i've noticed that i can't use my > 265-byte inode ext3 drives -- is there any effort to update it? If > not -- if you know where i should attempt to start please let me know > so i can start working on support (i have a few other people i know > interested in this) -- thanks and hope everyone is well There was a PR submitted for it and eventually a patch added to the PR. I've tested the patch given in the URL at the port and it works. We will start to see more of this as the newer version becomes more common in the wild. http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/124621 Would be nice to see this fixed in 7.1 but it may be too late for that. -- WXS