[ https://issues.apache.org/jira/browse/KUDU-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17727788#comment-17727788 ]
ASF subversion and git services commented on KUDU-3418: ------------------------------------------------------- Commit 355116aa602f6fc04716abdc8cafe82ec5bedd85 in kudu's branch refs/heads/branch-1.17.x from Ashwani Raina [ https://gitbox.apache.org/repos/asf?p=kudu.git;h=355116aa6 ] 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 <mre...@cloudera.com> Reviewed-by: Yingchun Lai <laiyingc...@apache.org> Tested-by: Yingchun Lai <laiyingc...@apache.org> Reviewed-on: http://gerrit.cloudera.org:8080/19944 Tested-by: Kudu Jenkins Reviewed-by: Ashwani Raina <ara...@cloudera.com> Reviewed-by: Alexey Serbin <ale...@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 > Fix For: 1.17.0 > > > 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)