From 0362ff63a5866bc55d0bcc9801f673a4e57f7dcc Mon Sep 17 00:00:00 2001 From: Sascha Wildner Date: Fri, 11 Jul 2014 23:27:42 +0200 Subject: [PATCH] Fix a couple of typos in a manpage and readme file. --- sbin/hammer/hammer.8 | 2 +- sys/dev/disk/dm/targets/dmirror/dmirror_notes.txt | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/sbin/hammer/hammer.8 b/sbin/hammer/hammer.8 index 2b66f4187f..59aef5ad91 100644 --- a/sbin/hammer/hammer.8 +++ b/sbin/hammer/hammer.8 @@ -172,7 +172,7 @@ The default is five seconds. Specify the maximum amount of memory .Nm will allocate during a dedup pass. -Specify a suffix 'm', 'g', or 't' for megabytes, gigabytes, or terrabytes. +Specify a suffix 'm', 'g', or 't' for megabytes, gigabytes, or terabytes. By default .Nm will allocate up to 1G of ram to hold CRC/SHA tables while running dedup. diff --git a/sys/dev/disk/dm/targets/dmirror/dmirror_notes.txt b/sys/dev/disk/dm/targets/dmirror/dmirror_notes.txt index 4901a00d3f..38b6ee4d78 100644 --- a/sys/dev/disk/dm/targets/dmirror/dmirror_notes.txt +++ b/sys/dev/disk/dm/targets/dmirror/dmirror_notes.txt @@ -14,7 +14,7 @@ are out of sync would be resynchronized. We want to avoid having to completely resynchronize the entire - contents of a potentitally multi-terrabyte drive if one is + contents of a potentially multi-terabyte drive if one is taken offline temporarily and then brought back online. * Allow mixed I/O errors on both drives making up the mirror @@ -266,7 +266,7 @@ When formatting a new mirror or when a drive is torn out and a new drive is added the drive(s) in question must be formatted. To avoid actually writing to all sectors of the drive, which would - take too long on multi-terrabyte drives and create unnecesary + take too long on multi-terabyte drives and create unnecesary writes on things like SSDs we instead of an UNINITIALIZED flag state in the descriptor. -- 2.41.0