All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valerie Clement <valerie.clement@bull.net>
To: "Jose R. Santos" <jrs@us.ibm.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Creating a >32bit blocks filesystem.
Date: Fri, 04 May 2007 16:58:35 +0200	[thread overview]
Message-ID: <463B4A1B.4070201@bull.net> (raw)
In-Reply-To: <20070503140804.463b20e1@naruto>

[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]

Jose R. Santos wrote:
> Hi folks,
> 
> I've been trying test a patch to set JBD2_FEATURE_INCOMPAT_64BIT, but
> I'm stuck just trying to test the patch since there doesn't seem to be
> a way to create a ext4 filesystem that has more than 32bit blocks.  It
> seems like e2fsprogs + Ted's patches don't support greater that 32bit
> block numbers while the the e2fsprogs 64bit patches from BULL create
> the filesystem but the kernel seems unable to mount.
> 
> Am I missing something?
> 
> -JRS

Hi Jose,
I began to port our modifications done for the 64-bit support against 
the new version of e2fsprogs Ted posted at the beginning of the week.
Note that it is *just* for test use as it breaks the backwards 
compatibility.
I did a few tests with a kernel 2.6.17-rc7 and it seems to work, at 
least mkfs, debugfs and fsck tools.

Get the new version of e2fsprogs at
ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs-interim/e2fsprogs-1.39-tyt3
and apply the patchset in attachment.

Hope this helps,
    Valérie

[-- Attachment #2: e2fsprogs-1.39-tyt3-64bit-patches.tar.gz --]
[-- Type: application/x-gzip, Size: 50733 bytes --]

  reply	other threads:[~2007-05-04 14:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-03 19:08 Creating a >32bit blocks filesystem Jose R. Santos
2007-05-04 14:58 ` Valerie Clement [this message]
2007-05-07 16:19   ` Jose R. Santos
2007-05-07 18:36     ` Jose R. Santos
2007-05-09 12:16     ` Valerie Clement
2007-05-09 13:55       ` Jose R. Santos
2007-05-09 14:57         ` Valerie Clement
2007-05-09 15:21           ` Eric Sandeen
2007-05-09 16:34             ` Jose R. Santos
2007-05-09 17:02               ` Eric Sandeen
2007-05-09 15:29           ` Jose R. Santos
2007-05-09 16:15           ` Andreas Dilger
2007-05-09 17:18   ` Eric Sandeen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=463B4A1B.4070201@bull.net \
    --to=valerie.clement@bull.net \
    --cc=jrs@us.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.