From: Ted Ts'o <tytso@mit.edu>
To: Tao Ma <tm@tao.ma>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: big allocation status
Date: Sat, 4 Jun 2011 15:11:35 -0400 [thread overview]
Message-ID: <20110604191135.GC1001@thunk.org> (raw)
In-Reply-To: <4DE9EE01.6070406@tao.ma>
On Sat, Jun 04, 2011 at 04:34:09PM +0800, Tao Ma wrote:
> Cool, but do you have a mkfs.ext4 that we can let the kernel part work
> happily? Or we have to add the feature by hand by editing the disk
> format. ;)
Grab the bigalloc-hack branch on the e2fsprogs git tree on
git.kernel.org. This will allow you to create bigalloc file systems
via "mke2fs -t ext4 -O bigalloc". Don't base anything on this branch;
the code is incredibly hacky, and not how the final bigalloc
support will be done.
- Ted
next prev parent reply other threads:[~2011-06-04 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 1:57 big allocation status Tao Ma
2011-06-04 3:38 ` Ted Ts'o
2011-06-04 8:34 ` Tao Ma
2011-06-04 19:11 ` Ted Ts'o [this message]
2011-06-06 23:04 ` Ted Ts'o
2011-06-07 2:01 ` Tao Ma
2011-06-27 10:25 ` Tao Ma
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=20110604191135.GC1001@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=tm@tao.ma \
/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).