Oops ...

On Tue, 2008-07-08 at 18:21 +0530, Girish Shilamkar wrote:
> Hi,	
> 	Here is the patch for same.
> 
> Thanks,
> Girish
> 
> On Mon, 2008-07-07 at 22:25 +0530, Girish Shilamkar wrote:
> > Hi,
> > 	The magic constant EXT_MAX_BLOCK = 0xffffffff in extents code is used
> > in some places to return "invalid block number", and to set the extent
> > length = "whole file" in other places.
> > 	So with >= 16 TB fs we would prefer to use it differently. We can have
> > EXT_UNSET_BLOCK = 1 to indicate "invalid block number" as it will never
> > be valid block for allocation. And for "whole file" usecase we can
> > continue using current EXT_MAX_BLOCK
> > 
> > Regards,
> > Girish
> > 
> > 
> > 
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html