From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Sandeen Subject: Re: [PATCH] fix ext2 allocator overflows above 31 bit blocks Date: Fri, 20 Apr 2007 18:14:47 -0500 Message-ID: <46294967.6070601@redhat.com> References: <4628F3ED.9040101@redhat.com> <20070420230208.GU5967@schatzie.adilger.int> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: Eric Sandeen , Linux Kernel Mailing List , ext4 development Return-path: Received: from mx1.redhat.com ([66.187.233.31]:36795 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751153AbXDTXOw (ORCPT ); Fri, 20 Apr 2007 19:14:52 -0400 In-Reply-To: <20070420230208.GU5967@schatzie.adilger.int> Sender: linux-ext4-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org Andreas Dilger wrote: > On Apr 20, 2007 12:10 -0500, Eric Sandeen wrote: >> If ext3 can do 16T, ext2 probably should be able to as well. >> There are still "int" block containers in the block allocation path >> that need to be fixed up. > > Yeah, but who wants to do 16TB e2fsck on every boot? I think there > needs to be some limits imposed for the sake of usability. I figure this is in the fine tradition of "enough rope to hang oneself" If you have 16T of filesystem you probably know enough to not hang yourself this way. *shrug* It's a bug, today. If we need another change to limit ext2 to 500G or something, fine by me. :) -Eric