[
https://issues.apache.org/jira/browse/KUDU-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857774#comment-16857774
]
Grant Henke commented on KUDU-2713:
-----------------------------------
[~tlipcon] Do you think this is critical enough to block a 1.10 release?
Otherwise I will bump the target to 1.11.0.
> FS misinterprets file block size as file system block size
> ----------------------------------------------------------
>
> Key: KUDU-2713
> URL: https://issues.apache.org/jira/browse/KUDU-2713
> Project: Kudu
> Issue Type: Bug
> Components: fs
> Reporter: Todd Lipcon
> Priority: Critical
>
> We recently saw a case where a cluster was using XFS with the 'largeio' mount
> option. This caused files on the drive to report a 4MB block size, even
> though the actual file system block size was the default 4kb. This caused the
> LBM to align all blocks up to 4MB and cause an enormous amount of wasted
> space.
> Instead of using the file's block size we should probably use statvfs() which
> reports the correct block size. Alternatively we could consider actually
> running a basic hole-punch test to determine the granularity of hole punches.
> Fixing this in a compatible way may also be a bit involved since changing the
> apparent block size of a system after the instance has been formatted will
> prevent it from starting.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
