Received-SPF: pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Tue, 2 Jul 2019 16:39:37 -0400
From:   "Theodore Ts'o" <tytso@mit.edu>
To:     James Bottomley <James.Bottomley@HansenPartnership.com>
Cc:     linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
        Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [BUG] mke2fs produces corrupt filesystem if badblock list
 contains a block under 251
Message-ID: <20190702203937.GG3032@mit.edu>
References: <1562021070.2762.36.camel@HansenPartnership.com>
 <20190702002355.GB3315@mit.edu>
 <1562028814.2762.50.camel@HansenPartnership.com>
 <20190702173301.GA3032@mit.edu>
 <1562095894.3321.52.camel@HansenPartnership.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1562095894.3321.52.camel@HansenPartnership.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-ext4-owner@vger.kernel.org
Precedence: bulk

On Tue, Jul 02, 2019 at 12:31:34PM -0700, James Bottomley wrote:
> Actually, this is giving me:
> 
> mke2fs: Operation not supported for inodes containing extents while
> creating huge files
> 
> Is that because it's an ext4 only feature?

That'll teach me not to send out a sequence like that without testing
it myself first.  :-)

Yeah, because one of the requirements was to make the file contiguous,
without any intervening indirect block or extent tree blocks, the
creation of the file is done manually, and at the time, I only
implemented it for extents, since the original goal of the goal was to
create really big files (hence the name of the feature "mk_hugefile"),
and using indirect blocks would be a huge waste of disk space.

It wouldn't be that hard for me to add support for indirect block
maps, or if you were going to convert things over so that the pa_risc
2nd stage boot loader can understand how to read from extents, that'll
allow this to work as well.

					- Ted