Bug 157675 - Man pages for mount are incorrect for sync on FAT and VFAT
Man pages for mount are incorrect for sync on FAT and VFAT
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: util-linux (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Karel Zak
Ben Levenson
Depends On:
Blocks: 156322
  Show dependency treegraph
Reported: 2005-05-13 13:19 EDT by Michael H. Warfield
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version: RHBA-2005-669
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-05 12:53:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael H. Warfield 2005-05-13 13:19:56 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050509 Fedora/1.0.3-5 Firefox/1.0.3

Description of problem:
Man pages for "mount" claim that the "sync" option is ignored by the FAT and VFAT file systems.  This is not (any longer) true.  VFAT file systems do honor the sync option and, consequently, damage and destroy flash devices with VFAT file systems mounted this way.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Read man pages for mount and look for VFAT and sync

Actual Results:  Says FAT and VFAT ignore sync option

Expected Results:  Should say that sync may cause damage with FAT and VFAT file systems

Additional info:

Related bug filed under hal for destruction of flash keys when mounted with "sync" option.
Comment 1 Karel Zak 2005-06-16 06:30:17 EDT
The fix of man page will be available in the next FC4 update (util-linux-2.12p-9.4).
Comment 8 Red Hat Bugzilla 2005-10-05 12:53:18 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.