Red Hat Bugzilla – Bug 105595
modifying loopback-mounted filesystem doesn't change file's timestamps
Last modified: 2009-07-14 12:51:26 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Description of problem:
After loopback-mounting a file containing an ext2 filesystem, adding and
modifying files, and umounting it, the timestamps of the file remain unchanged.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.dd if=/dev/zero of=file.img bs=1k count=1440
2.mke2fs -f file.img
4.ls -l file.img
5.mount -o loop file.img /tmp/mnt
7.ls -l file.img
Actual Results: The timestamps printed by ls are the same
Expected Results: They shouldn't be (unless you do it really fast! :-)
fc1 - eol
This is actually still present in the latest testing kernel for FC3:
kernel-2.6.9-1.698_FC3. Tested in x86_64 this time, so assuming it affects all
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
Problem still present in kernel-2.6.13-1.1548_FC5.
I actually have this problem under 2.6.16-1.2111_FC5 ... I just ran into this
while messing around with floppy images. When I updated a file in the image,
subversion couldn't see that the file was updated until I touched the file.
just for reference sake, I ran this on x86_64 and i386 based kernels. Same
I just tested this on i386 FC6T3 and it is still there. Please move this ticket
Linux testsrv 2.6.17-1.2647.fc6 #1 SMP Wed Sep 13 12:51:50 EDT 2006 i686 i686
Retested with the latest FC5 X86_64 kernel and I still see an issue with it.
Linux home-desk 2.6.18-1.2239.fc5 #1 SMP Fri Nov 10 12:51:06 EST 2006 x86_64
x86_64 x86_64 GNU/Linux
I guess I should actually read the original ticket information:
"After loopback-mounting a file containing an ext2 filesystem,"
mount a DOS 6.20 floppy image via the loop back device:
mount -o loop DOS_Floppy.bin /mnt/floppy
Modify the contents of that image
Time/date stuff doesn't change.
I found this while trying to manage a large amount of floppy images for flash
updating BIOS's and such and keeping the images version controlled in
subversion. In my case, after I update the ROM files on the floppy images, I
have to 'touch' the image to get subversion to notice that the image has changed.
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.
If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we're following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
I just tested the failure case against kernel-220.127.116.11-64.fc8 and
The problem persists still. svn is unable to see that the image file has
changed after I mount it via loopback, edit a file and then unmount the image.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. 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 '9'.
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 9'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 9 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:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.