diff options
author | Daniel Gerzo <danger@FreeBSD.org> | 2006-09-08 13:47:39 +0000 |
---|---|---|
committer | Daniel Gerzo <danger@FreeBSD.org> | 2006-09-08 13:47:39 +0000 |
commit | d6649c2569aee570c2a82a8e4c8ed2a2a09e3673 (patch) | |
tree | b11d64e9803e120ee5c551efee75ab26f2f45c0f | |
parent | 46ee0837c250b56466fba03d76f3a80f6c5408bd (diff) | |
download | src-d6649c2569aee570c2a82a8e4c8ed2a2a09e3673.tar.gz src-d6649c2569aee570c2a82a8e4c8ed2a2a09e3673.zip |
Re-word the description of the "async" flag.
Suggested by: Milos Vyletel (mv@rulez.sk)
Reviewed by: ru
Approved by: keramida (mentor), trhodes (mentor)
Notes
Notes:
svn path=/head/; revision=162154
-rw-r--r-- | sbin/mount/mount.8 | 9 |
1 files 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 |