From d6649c2569aee570c2a82a8e4c8ed2a2a09e3673 Mon Sep 17 00:00:00 2001 From: Daniel Gerzo Date: Fri, 8 Sep 2006 13:47:39 +0000 Subject: [PATCH] Re-word the description of the "async" flag. Suggested by: Milos Vyletel (mv@rulez.sk) Reviewed by: ru Approved by: keramida (mentor), trhodes (mentor) --- sbin/mount/mount.8 | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/sbin/mount/mount.8 b/sbin/mount/mount.8 index ec3ca96c4542..03945222ce97 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