From: Andrew Morton Subject: Re: Updated ext4/jbd2 patches based on 2.6.19-rc1 Date: Thu, 5 Oct 2006 20:55:26 -0700 Message-ID: <20061005205526.7fe744f5.akpm@osdl.org> References: <1160072610.8508.12.camel@kleikamp.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: ext4 development Return-path: Received: from smtp.osdl.org ([65.172.181.4]:24468 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S1751765AbWJFDzb (ORCPT ); Thu, 5 Oct 2006 23:55:31 -0400 To: Dave Kleikamp In-Reply-To: <1160072610.8508.12.camel@kleikamp.austin.ibm.com> Sender: linux-ext4-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On Thu, 05 Oct 2006 13:23:30 -0500 Dave Kleikamp wrote: > I have rebuilt the ext4/jbd2 patches against linux-2.6.19-rc1. The > patch set is located at > ftp://kernel.org/pub/linux/kernel/people/shaggy/ext4/2.6.19-rc1/ext4-patches-2.6.19-rc1.tar.gz > So let me see if I have this right. You grab Alexandre's kit from http://www.bullopensource.org/ext4/20060926/ and a plain old `mke2fs -j' gives a filesystem which will mount as ext3 or ext4. If you then mount this filesystem with `-t ext4dev -o extents', it becomes incompatible with the ext3 driver. Yes? What else aren't we being told? ;)