Messages in this thread Patch in this message | | | Subject | util-linux: Add explanation for new mount options flushonfsync and noflushonfsync to mount(8) man page | From | Fernando Luis Vázquez Cao <> | Date | Thu, 12 Feb 2009 19:38:01 +0900 |
| |
Signed-off-by: Fernando Luis Vazquez Cao <fernando@oss.ntt.co.jp> ---
diff -urp mount-orig/mount.8 mount/mount.8 --- mount-orig/mount.8 2009-01-29 15:50:50.000000000 +0900 +++ mount/mount.8 2009-01-29 15:40:39.000000000 +0900 @@ -649,6 +649,18 @@ current modify or change time. (Similar mutt or other applications that need to know if a file has been read since the last time it was modified.) .TP +.B flushonfsync +Force block device flush on fsync()/fdatasync(). When using storage equipped +with write caches that can be explicitly flushed by the kernel, this guarantees +that the data/metadata actually made it to the physical media after invoking +the respective file data/metadata synchronization system call. +.TP +.B noflushonfsync +Do not force a flush of the backing device's write cache when a file +data/metadata synchronization system call is executed. Unless the device is +equipped with a battery-backup write cache, this behavior can cause data loss +and/or file system corruption in the event of a power failure. +.TP .B noauto Can only be mounted explicitly (i.e., the .B \-a
| |