Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762032AbXH3BAP (ORCPT ); Wed, 29 Aug 2007 21:00:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758126AbXH3BAA (ORCPT ); Wed, 29 Aug 2007 21:00:00 -0400 Received: from netops-testserver-3-out.sgi.com ([192.48.171.28]:51223 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1757804AbXH3A77 (ORCPT ); Wed, 29 Aug 2007 20:59:59 -0400 Date: Wed, 29 Aug 2007 17:59:58 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Mingming Cao cc: linux-fsdevel@vger.kernel.org, adilger@clusterfs.com, sho@tnes.nec.co.jp, ext4 development , linux-kernel@vger.kernel.org Subject: Re: [RFC 1/4] Large Blocksize support for Ext2/3/4 In-Reply-To: <1188434857.3799.76.camel@localhost.localdomain> Message-ID: References: <20070828190551.415127746@sgi.com> <20070828190735.292638294@sgi.com> <1188432669.3799.35.camel@localhost.localdomain> <1188434857.3799.76.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 882 Lines: 20 On Wed, 29 Aug 2007, Mingming Cao wrote: > It's quite simple to support large block size in ext2/3/4, mostly just > enlarge the block size limit. But it is NOT possible to have 64kB > blocksize on ext2/3/4 without some changes to the directory handling > code. The reason is that an empty 64kB directory block would have a > rec_len == (__u16)2^16 == 0, and this would cause an error to be hit in > the filesystem. The proposed solution is to put 2 empty records in such > a directory, or to special-case an impossible value like rec_len = > 0xffff to handle this. Ahh. Good. I could add the path to the large blocksize patchset? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/