From: Mingming Cao <cmm@us.ibm.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Mike Waychison <mikew@google.com>, Theodore Tso <tytso@mit.edu>,
Andrew Morton <akpm@linux-foundation.org>,
Sreenivasa Busam <sreenivasac@google.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: fallocate support for bitmap-based files
Date: Sat, 30 Jun 2007 10:31:45 -0400 [thread overview]
Message-ID: <1183213905.9505.29.camel@localhost.localdomain> (raw)
In-Reply-To: <20070630051436.GB5535@schatzie.adilger.int>
On Sat, 2007-06-30 at 01:14 -0400, Andreas Dilger wrote:
> On Jun 29, 2007 18:26 -0400, Mike Waychison wrote:
> > Andreas Dilger wrote:
> > >I don't think ext2 is safe for > 8TB filesystems anyways, so this
> > >isn't a huge loss.
> >
> > This is reference to the idea of overloading the high-bit and not
> > related to the >PAGE_SIZE blocks correct?
>
> Correct - just that the high-bit use wouldn't unduely impact the
> already-existing 8TB limit of ext2.
>
The 8TB limit on mainline ext2 was simplely caused by kernel block
variable type bugs. The bug fixes were ported back from ext3 to ext2,
when reservation+simple-multiple-balloc were backported from ext3 to
ext2. I believe ext2 in mm tree is able to address 16TB in the kernel
side. Not sure if there are remaining work to be done in e2fsck to
handle 16TB ext2, but I assume it's not huge work.
Mingming
next prev parent reply other threads:[~2007-06-30 14:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 20:01 fallocate support for bitmap-based files Andrew Morton
2007-06-29 20:36 ` Dave Kleikamp
2007-06-29 20:52 ` Mike Waychison
2007-06-29 21:24 ` Dave Kleikamp
2007-06-29 20:55 ` Theodore Tso
2007-06-29 21:38 ` Andrew Morton
2007-06-29 22:07 ` Mike Waychison
2007-07-04 23:11 ` Valerie Henson
2007-07-06 21:15 ` Mike Waychison
2007-06-29 21:46 ` Andreas Dilger
2007-06-29 22:26 ` Mike Waychison
2007-06-30 5:14 ` Andreas Dilger
2007-06-30 14:31 ` Mingming Cao [this message]
2007-06-30 14:13 ` Mingming Cao
2007-06-30 17:29 ` Andreas Dilger
2007-07-02 14:44 ` Mingming Cao
2007-07-02 17:44 ` Badari Pulavarty
2007-07-06 21:33 ` Mike Waychison
2007-07-07 2:05 ` Badari Pulavarty
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=1183213905.9505.29.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=adilger@clusterfs.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=mikew@google.com \
--cc=sreenivasac@google.com \
--cc=tytso@mit.edu \
/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