Looks good for me.
Thanks
Gang
>>>
> Some versions of tar assume that files with st_blocks == 0 do not
> contain any data and will skip reading them entirely. See also
> commit 9206c561554c ("ext4: return non-zero st_blocks for inline data").
>
> Signed-off-by: John Haxby <john.ha...@oracle.com>
> ---
> fs/ocfs2/file.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/fs/ocfs2/file.c b/fs/ocfs2/file.c
> index 0e5b451..d631279 100644
> --- a/fs/ocfs2/file.c
> +++ b/fs/ocfs2/file.c
> @@ -1302,6 +1302,14 @@ int ocfs2_getattr(struct vfsmount *mnt,
> }
>
> generic_fillattr(inode, stat);
> + /*
> + * If there is inline data in the inode, the inode will normally not
> + * have data blocks allocated (it may have an external xattr block).
> + * Report at least one sector for such files, so tools like tar, rsync,
> + * others don't incorrectly think the file is completely sparse.
> + */
> + if (unlikely(OCFS2_I(inode)->ip_dyn_features & OCFS2_INLINE_DATA_FL))
> + stat->blocks += (stat->size + 511)>>9;
>
> /* We set the blksize from the cluster size for performance */
> stat->blksize = osb->s_clustersize;
> --
> 2.5.0
>
>
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel@oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel
