All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Cc: Johann Lombardi <johann.lombardi@bull.net>,
	"Amit K. Arora" <aarora@linux.vnet.ibm.com>,
	Dave Chinner <dgc@sgi.com>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.21-ext4-1
Date: Mon, 30 Apr 2007 11:58:56 -0400	[thread overview]
Message-ID: <20070430155856.GC10604@thunk.org> (raw)
In-Reply-To: <E1HiXab-0001QX-Sk@candygram.thunk.org>

Sorry, I forgot to include the URL's where ext4 development patchset
can be found:

ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/2.6.21-ext4-1

					- Ted

On Mon, Apr 30, 2007 at 11:14:57AM -0400, Theodore Ts'o wrote:
> 
> I've respun the ext4 development patchset, with Amit's updated fallocate
> patches.  I've added Dave's patch to add ia64 support to the fallocate
> system call, but *not* the XFS fallocate support patches.  (Probably
> better for them to live in an xfs tree, where they can more easily
> tested and updated.)  Yes, we haven't reached complete closure on the
> fallocate system call calling convention, but it's enough for us to get
> more testing in -mm.
> 
> Also added Johann's jbd2-stats-through-procfs patches; it provides
> useful help in turning the size of the journal, which will be useful in
> benchmarking efforts.  In addition, Alex Tomas's patch to free
> just-allocated patches when there is an error inserting the extent into
> the extent tree has also been included.
> 
> The patches have been compile-tested on x86, and compile/run-tested on
> x86/UML.  Would appreciate reports about testing on other platforms.
> 
> Thanks,
> 
> 						- Ted
> 
> P.S.  One bug which I've noted --- if there is a failure due to disk
> filling up, running e2fsck on the filesystem will show that the i_blocks
> fields on the inodes where there was a failure to allocate disk blocks
> are left incorrect.  I'm guessing this is a bug in the delayed
> allocation patches.  Alex, when you have a moment, could you take a
> look?  Thanks!!

  reply	other threads:[~2007-04-30 15:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 15:14 2.6.21-ext4-1 Theodore Ts'o
2007-04-30 15:58 ` Theodore Tso [this message]
2007-04-30 16:24 ` 2.6.21-ext4-1 Alex Tomas
2007-04-30 17:16 ` 2.6.21-ext4-1 Jeff Garzik
2007-04-30 17:45   ` 2.6.21-ext4-1 Theodore Tso
2007-05-07 20:56 ` 2.6.21-ext4-1 Mingming Cao
2007-05-08  2:50   ` 2.6.21-ext4-1 David Chinner
2007-05-08 22:05     ` 2.6.21-ext4-1 Mingming Cao
2007-05-08 23:24       ` 2.6.21-ext4-1 David Chinner
2007-05-09 14:36         ` 2.6.21-ext4-1 Amit K. Arora
2007-05-09 14:52           ` 2.6.21-ext4-1 Eric Sandeen

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=20070430155856.GC10604@thunk.org \
    --to=tytso@mit.edu \
    --cc=aarora@linux.vnet.ibm.com \
    --cc=dgc@sgi.com \
    --cc=johann.lombardi@bull.net \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@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.