From: Valerie Aurora Henson <vaurora@redhat.com>
To: linux-ext4@vger.kernel.org
Subject: 64-bit e2fsprogs tree for testing
Date: Thu, 22 Jan 2009 19:28:15 -0500 [thread overview]
Message-ID: <20090123002815.GJ12643@shell> (raw)
Hi folks,
The e2fsprogs 64-bit branch is available for public testing. This
branch adds support for creating, checking, etc. ext4 file systems
with more than 2^32 blocks - i.e., more than 16TB on most systems.
This is for TESTING ONLY - don't put any data you care about on it!
The public git repository is available here:
git://git.kernel.org/pub/scm/fs/ext2/val/e2fsprogs.git
The branch is "64bit".
Known bugs:
* compilation of programs using certain libe2p routines may fail
(chattr, lsattr)
* fsck will fail if directories contain blocks above the 32-bit
boundary
In general, this is very lightly tested.
Please only test against the latest ext4 kernel bits from:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
Please report bugs to this mailing list and cc'd to me if possible.
I am personally testing this using a sparse backing file on XFS, e.g.:
# dd if=/dev/zero of=/xfs/testfile bs=4096 seek=5G count=1
# ./misc/mke2fs /xfs/testfile
# mount -o loop /xfs/testfile /mnt
# dmesg | tail # to make sure it actually mounted as ext4, etc.
Unfortunately, you can't use ext4 itself to host the backing file,
since it has a limit of 2^32 blocks per file.
Thank you in advance!
-VAL
next reply other threads:[~2009-01-23 0:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 0:28 Valerie Aurora Henson [this message]
2009-01-27 5:29 ` 64-bit e2fsprogs tree for testing Valerie Aurora Henson
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=20090123002815.GJ12643@shell \
--to=vaurora@redhat.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.