anchor.diff:  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.
  
positive.code: ----
  
  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.
  
  [[memory_limits]]
  === Memory Limits
  
negative.code:  - 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 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
  