Bug 427465 - VFAT file timestamp problems
Summary: VFAT file timestamp problems
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 8
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-01-03 23:52 UTC by John William
Modified: 2009-01-29 19:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-01-09 05:41:44 UTC

Attachments (Terms of Use)

Description John William 2008-01-03 23:52:05 UTC
Description of problem:

File time stamps change and are not preserved across VFAT mount/unmount cycles.

File time stamps do not work correctly on VFAT devices across mount/unmount cycles.

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

How reproducible: Always

Steps to Reproduce:
$ touch ~/dos/testfile
$ stat ~/dos/testfile
Access: 2008-01-03 17:44:24.000000000 -0600
Modify: 2008-01-03 17:44:24.000000000 -0600
Change: 2008-01-03 17:44:24.000000000 -0600
$ umount dos ; mount /dev/sda1 dos
$ stat ~/dos/testfile
Access: 2008-01-03 00:00:00.000000000 -0600
Modify: 2008-01-03 17:44:24.000000000 -0600
Change: 2008-01-03 17:44:24.000000000 -0600
$ touch ~/dos/testfile
$ stat ~/dos/testfile
Access: 2008-01-03 17:44:51.000000000 -0600
Modify: 2008-01-03 17:44:51.000000000 -0600
Change: 2008-01-03 17:44:51.000000000 -0600
$ umount dos ; mount /dev/sda1 dos
$ stat ~/dos/testfile
Access: 2008-01-03 00:00:00.000000000 -0600
Modify: 2008-01-03 17:44:50.000000000 -0600
Change: 2008-01-03 17:44:51.000000000 -0600
Actual results:
(see above)

Expected results:
The modification time seems to be off by one second after the remount. This
seems to be a kernel problem, as this was not a problem with F7, and copying the
file in Windows Explorer correctly sets the time (dual boot machine).

Additional info:

Comment 1 Bug Zapper 2008-11-26 09:16:55 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 2 Bug Zapper 2009-01-09 05:41:44 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Nathan Schrenk 2009-01-29 19:30:46 UTC
This bug still exists in Fedora 9.

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