[jira] [Commented] (KUDU-3418) Punch hole feature not supported on disks with FDE enabled

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692470#comment-17692470 ] 

ASF subversion and git services commented on KUDU-3418:
-------------------------------------------------------

Commit 38b864082f1e230c181d89b8d1a764c6af7b7506 in kudu's branch refs/heads/master from Ashwani Raina
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=38b864082 ]

KUDU-3418 Improve hole punching error message description.

Kudu LBM relies on hole punching support from filesystem.
However, it is possible that even with supported kernel version
and fileystem type, hole punching feature may not work.
Hole punching uses fallocate system call to do its job.
But it is evident from fallocate system call implementation of
ext4, that encrypted inodes are not supported.
Refer: https://elixir.bootlin.com/linux/latest/source/fs/ext4/extents.c#L4685

The same description is added to kHolePunchErrorMsg used by
CheckHolePunch method that checks for hole punching support.

Change-Id: If87401012052508b9cdf394cd33dc32fb58659d4
Reviewed-on: http://gerrit.cloudera.org:8080/19525
Reviewed-by: Mahesh Reddy <mr...@cloudera.com>
Reviewed-by: Yingchun Lai <la...@apache.org>
Tested-by: Yingchun Lai <la...@apache.org>


> Punch hole feature not supported on disks with FDE enabled
> ----------------------------------------------------------
>
>                 Key: KUDU-3418
>                 URL: https://issues.apache.org/jira/browse/KUDU-3418
>             Project: Kudu
>          Issue Type: Bug
>          Components: supportability
>    Affects Versions: 1.14.0, 1.15.0, 1.16.0
>            Reporter: Ashwani Raina
>            Assignee: Ashwani Raina
>            Priority: Trivial
>              Labels: prerequisite
>
> Some devices have security feature of "Full Disk Encryption" enabled on disks.
> For such cases, punch hole feature inside Ext type filesystem is not supported on most of the kernel versions.
> To run without hole punching (at the cost of some efficiency and scalability), Kudu needs to be reconfigured to use the file block manager.
> This Jira is to track the work to note this in Kudu documentation if not already present.
> Also, if possible check if error message can be made more clear when kudu cluster configuration hits this issue.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)