From: Valerie Clement <valerie.clement@bull.net>
To: anton.andreev@fmi.uni-sofia.bg
Cc: linux-ext4@vger.kernel.org
Subject: Re: 64 bit support for ext4 problem
Date: Tue, 31 Jul 2007 11:39:09 +0200 [thread overview]
Message-ID: <46AF033D.6020909@bull.net> (raw)
In-Reply-To: <46AEE61B.5000207@fmi.uni-sofia.bg>
Anton Andreev wrote:
> Hi,
>
> I want to try my ext4 to be 64 bit.
>
> I could not patch e2fsprogs-1.39
> <http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.39.tar.gz>
> with
> http://www.bullopensource.org/ext4/patches/ext4-e2fsprogs-1.39.patch.tar
> . I would appreciate if someone tell me exactly how to do that.
>
> Does the newest version of e2fsprogs
> <http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.39.tar.gz>
> supports the features in the patch?
Hi Anton,
you need to patch the e2fsprogs only if you want to create an ext4
filesystem larger than 16 TB with 4KB block size. If it is your case,
I could send you a more recent version of patches. Let me know.
Ext4 supports 48-bit physical block numbers, not yet 64-bit physical
block numbers; this is due to the use of extents mapping.
If you want to use the extent format (mount -t ext4dev -o extents), I
think you should use the latest version of e2fsprogs available here:
http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.40.2.tar.gz
ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/e2fsprogs-1.40.2.tar.gz
This version should integrate the extents capability.
Remember that if you use extents, your filesystem will no longer be
mountable by ext3.
Regards,
Valérie
next prev parent reply other threads:[~2007-07-31 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 7:34 64 bit support for ext4 problem Anton Andreev
2007-07-31 9:39 ` Valerie Clement [this message]
2007-07-31 14:35 ` Andreas Dilger
2007-07-31 15:03 ` Valerie Clement
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=46AF033D.6020909@bull.net \
--to=valerie.clement@bull.net \
--cc=anton.andreev@fmi.uni-sofia.bg \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).