Re: [PATCH 4/6] Documentation/fiemap: Document DATA_COMPRESSED and PHYS_LENGTH flags

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

 



On Jul 30, 2014, at 11:18 AM, David Sterba <dsterba@xxxxxxx> wrote:
> @@ -143,6 +148,16 @@ unmounted, and then only if the FIEMAP_EXTENT_ENCODED flag is
> clear; user applications must not try reading or writing to the
> filesystem via the block device under any other circumstances.
> 
> +* FIEMAP_EXTENT_PHYS_LENGTH
> +If set then fe_phys_length is valid and contains the physical size of the
> +extent.
> +
> +* FIEMAP_EXTENT_DATA_COMPRESSED
> +  - This will also set FIEMAP_EXTENT_ENCODED
> +The data in this extent has been compressed by the file system. When
> +set, fe_phys_length contains the physical extent length in bytes. The
> +value may be rounded depending on the filesystem implementation.

When DATA_COMPRESSED is set, then PHYS_LENGTH should always be set,
since it is using fe_phys_length.

Cheers, Andreas





Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail


[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux