Re: [Ext4 punch hole 1/5] Ext4 Punch Hole Support: Convert Blocks to Uninit Exts

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

 



On Mar 2, 2011, at 3:23 PM, Dave Chinner wrote:

> 
> XFS_IOC_ZERO_RANGE converts a range to unwritten extents, not
> uninitialised extents. An uninitialised extent is one that is
> allocated but had not data written to it (i.e. contains stale data),
> while an unwritten/preallocated extent is guaranteed to contain
> zeros.  This may be just a terminology issue, but we should try to
> use the same jargon across all filesystems...

What is the difference from the user's perspective?  If the read from
from an uninitialized extent, what do they get back?   And if the read
from an unwritten extent, what do they get back?   In ext4, in both
cases we would return all zero's.

For XFS, why is it important to maintain the distinction between these
two concept?

Just trying to understand,

-- Ted


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


[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux