From: "Theodore Ts'o" Subject: 2.6.21-ext4-1 Date: Mon, 30 Apr 2007 11:14:57 -0400 Message-ID: Cc: Johann Lombardi , "Amit K. Arora" , Dave Chinner , linux-kernel@vger.kernel.org To: linux-ext4@vger.kernel.org Return-path: Received: from thunk.org ([69.25.196.29]:52658 "EHLO thunker.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755453AbXD3PPG (ORCPT ); Mon, 30 Apr 2007 11:15:06 -0400 Sender: linux-ext4-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org 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!!