Repository: kudu Updated Branches: refs/heads/master 4ebfbe418 -> ba955733d
docs: add troubleshooting info on detecting ext2 and ext3 filesystems Change-Id: Ic4917e144690943e43bf5aa380b59379669846d9 Reviewed-on: http://gerrit.cloudera.org:8080/9871 Reviewed-by: Todd Lipcon <t...@apache.org> Tested-by: Kudu Jenkins Project: http://git-wip-us.apache.org/repos/asf/kudu/repo Commit: http://git-wip-us.apache.org/repos/asf/kudu/commit/ba955733 Tree: http://git-wip-us.apache.org/repos/asf/kudu/tree/ba955733 Diff: http://git-wip-us.apache.org/repos/asf/kudu/diff/ba955733 Branch: refs/heads/master Commit: ba955733d07dda66d4b1c9191966e8db12744762 Parents: 4ebfbe4 Author: Adar Dembo <a...@cloudera.com> Authored: Fri Mar 30 12:24:49 2018 -0700 Committer: Adar Dembo <a...@cloudera.com> Committed: Fri Mar 30 21:46:19 2018 +0000 ---------------------------------------------------------------------- docs/troubleshooting.adoc | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/kudu/blob/ba955733/docs/troubleshooting.adoc ---------------------------------------------------------------------- diff --git a/docs/troubleshooting.adoc b/docs/troubleshooting.adoc index ef6ad15..b5c5ae1 100644 --- a/docs/troubleshooting.adoc +++ b/docs/troubleshooting.adoc @@ -39,11 +39,9 @@ depends upon your operation system kernel version and local filesystem implement - RHEL or CentOS 6.4 or later, patched to kernel version of 2.6.32-358 or later. Unpatched RHEL or CentOS 6.4 does not include a kernel with support for hole punching. - Ubuntu 14.04 includes version 3.13 of the Linux kernel, which supports hole punching. - - Newer versions of the EXT4 or XFS file systems support hole punching, but EXT3 does - not. Older versions of XFS that do not support hole punching return a `EOPNOTSUPP` - (operation not supported) error. Older versions of either EXT4 or XFS that do - not support hole punching cause Kudu to emit an error message such as the following - and to fail to start: + - Newer versions of the ext4 and xfs filesystems support hole punching. Older versions + that do not support hole punching will cause Kudu to emit an error message such as the + following and to fail to start: + ---- Error during hole punch test. The log block manager requires a @@ -54,6 +52,15 @@ Kudu with --block_manager=file. Refer to the Kudu documentation for more details. Raw error message follows. ---- +[NOTE] +ext4 mountpoints may actually be backed by ext2 or ext3 formatted devices, which do not +support hole punching. The hole punching test will fail when run on such filesystems. There +are several different ways to determine whether an ext4 mountpoint is backed by an ext2, +ext3, or ext4 formatted device; see link:https://unix.stackexchange.com/q/60723[this Stack +Exchange post] for details. + +link:administration.html#change_dir_config[Changing Directory Configurations] documentation. + Without hole punching support, the log block manager is unsafe to use. It won't ever delete blocks, and will consume ever more space on disk. @@ -487,7 +494,7 @@ User stack: ---- These traces can be useful for diagnosing root-cause latency issues when they are caused by systems -below Kudu, such as disk controllers or file systems. +below Kudu, such as disk controllers or filesystems. [[memory_limits]] === Memory Limits
