From: "Jose R. Santos" <jrs@us.ibm.com>
To: Avantika Mathur <mathur@linux.vnet.ibm.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Ext4 devel interlock meeting minutes (July 30, 2007)
Date: Fri, 3 Aug 2007 21:42:22 -0500 [thread overview]
Message-ID: <20070803214222.2e0999f8@gara> (raw)
In-Reply-To: <46B3B2A5.9000307@linux.vnet.ibm.com>
On Fri, 03 Aug 2007 15:56:37 -0700
Avantika Mathur <mathur@linux.vnet.ibm.com> wrote:
> Flexible Block Groups:
> - Jose is trying to see why fsck is not working. once this is resolved,
> the feature will be complete.
Not quite true. Solving the fsck issue means that we can do more
thorough testing of the performance impacts of packaging meta-data
closer together. The patches do not currently remove the 512TB limit
imposed by the number of block groups, which is something that I also
plan to address on this feature.
-JRS
next prev parent reply other threads:[~2007-08-04 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 22:56 Ext4 devel interlock meeting minutes (July 30, 2007) Avantika Mathur
2007-08-04 2:42 ` Jose R. Santos [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-07 6:58 Avantika Mathur
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=20070803214222.2e0999f8@gara \
--to=jrs@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mathur@linux.vnet.ibm.com \
/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).