anchor.diff:  are full.
   
   In 1.7.0 and later, new tablets are assigned a disk group consisting of
  --fs_target_data_dirs_per_tablet data dirs (default 3). If Kudu is not configured
  -with enough data directories for a full disk group, all data directories are
  -used. When a data directory is full, Kudu will stop writing new data to it and
  -each tablet that uses that data directory will write new data to other data
  -directories within its group. If all data directories for a tablet are full, Kudu
  -will crash. Periodically, Kudu will check if full data directories are still
  -full, and will resume writing to those data directories if space has become
  -available.
  +`--fs_target_data_dirs_per_tablet` data dirs (default 3). If Kudu is not
  +configured with enough data directories for a full disk group, all data
  +directories are used. When a data directory is full, Kudu will stop writing new
  +data to it and each tablet that uses that data directory will write new data to
  +other data directories within its group. If all data directories for a tablet
  +are full, Kudu will crash. Periodically, Kudu will check if full data
  +directories are still full, and will resume writing to those data directories
  +if space has become available.
   
   If Kudu does crash because its data directories are full, freeing space on the
   full directories will allow the affected daemon to restart and resume writing.
  
positive.code: ----
  +
  
  . Modify the values of the `fs_data_dirs` flags for the updated sever. If using
    CM, make sure to only update the configurations of the updated server, rather
    than of the entire Kudu service.
  
  
negative.code: $ sudo service kudu-tserver start
  ----
  +
  
  . Use `ksck` to ensure Kudu returns to a healthy state before resuming normal
    operation.
  
  
  [[disk_failure_recovery]]
  