summaryrefslogtreecommitdiffstats
path: root/sbin/mount
diff options
context:
space:
mode:
authordanger <danger@FreeBSD.org>2006-09-08 13:47:39 +0000
committerdanger <danger@FreeBSD.org>2006-09-08 13:47:39 +0000
commit271e1a38791824da57527f2e960cbdf174835222 (patch)
treeb11d64e9803e120ee5c551efee75ab26f2f45c0f /sbin/mount
parentdd3e975df23621511b2ba0708983e25cccbc518a (diff)
downloadFreeBSD-src-271e1a38791824da57527f2e960cbdf174835222.zip
FreeBSD-src-271e1a38791824da57527f2e960cbdf174835222.tar.gz
Re-word the description of the "async" flag.
Suggested by: Milos Vyletel (mv@rulez.sk) Reviewed by: ru Approved by: keramida (mentor), trhodes (mentor)
Diffstat (limited to 'sbin/mount')
-rw-r--r--sbin/mount/mount.89
1 files changed, 6 insertions, 3 deletions
diff --git a/sbin/mount/mount.8 b/sbin/mount/mount.8
index ec3ca96..0394522 100644
--- a/sbin/mount/mount.8
+++ b/sbin/mount/mount.8
@@ -131,9 +131,12 @@ All
to the file system should be done asynchronously.
This is a
.Em dangerous
-flag to set,
-and should not be used unless you are prepared to recreate the file
-system should your system crash.
+flag to set, since it does not guarantee that the file system structure
+on the disk will remain consistent.
+For this reason, the
+.Cm async
+flag should be used sparingly, and only when some data recovery
+mechanism is present.
.It Cm current
When used with the
.Fl u
OpenPOWER on IntegriCloud