From d9182d75db8ba73118f03cb5ac8139902ab8a6f0 Mon Sep 17 00:00:00 2001 From: DanHam Date: Sat, 14 Apr 2018 00:08:03 +0100 Subject: [PATCH] Fix a couple of typos --- storage/storagedriver/device-mapper-driver.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/storage/storagedriver/device-mapper-driver.md b/storage/storagedriver/device-mapper-driver.md index 9dd8d4117d..9c0178dad4 100644 --- a/storage/storagedriver/device-mapper-driver.md +++ b/storage/storagedriver/device-mapper-driver.md @@ -404,7 +404,7 @@ assumes that the Docker daemon is in the `stopped` state. Do not rely on LVM auto-extension alone. The volume group automatically extends, but the volume can still fill up. You can monitor free space on the volume using `lvs` or `lvs -a`. Consider using a monitoring -tool at the OS level, such a Nagios. +tool at the OS level, such as Nagios. To view the LVM logs, you can use `journalctl`: @@ -414,7 +414,7 @@ $ journalctl -fu dm-event.service If you run into repeated problems with thin pool, you can set the storage option `dm.min_free_space` to a value (representing a percentage) in -`/etc/docker.daemon.json`. For instance, setting it to `10` ensures +`/etc/docker/daemon.json`. For instance, setting it to `10` ensures that operations fail with a warning when the free space is at or near 10%. See the [storage driver options in the Engine daemon reference](/engine/reference/commandline/dockerd/#storage-driver-options){: target="_blank" class="_"}.