Re: [PATCH 0/4] Fiemap, an extent mapping ioctl - round 2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Andreas Dilger wrote:

>>    - The filesystem's internal representation may have _many_ more
>>      extents than the contiguous layout.  E.g. a 4GiB file might have
>>      65536 x 64kiB extents on some filesystem, or 1 extent when
>>      merged.  Is it ever useful to return the much larger list?
> 
> It seems unlikely to consider this an "extent based" filesystem, and
> I'd treat it as a block-based filesystem internally and merge it...
> Yes, for ext4 it must split the extents at 128MB boundaries (1 group),
> but because of the on-disk metadata it isn't yet possible to allocate
> larger extents anyways.

aside: even w/ metadata out of the way the ext4 extent format is still
capped at 128M per extent right, even if they're contiguous.  Which led
me to the little though experiment about hm, is this 1G file 1 extent or
8 and what should fiemap return...

-Eric

--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux