Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-2129

Database file timestamp is never updated...

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 1.6.1
    • Component/s: None
    • Labels:
      None
    • Environment:
      Linux Fedora Core 8, running on AWS EC2 32-bit server.
      Also, Linux Fedora 13, running on AWS EC2 64-bit server.
    • Linux

      The timestamp of the database file never changes, even if writes are done to the DB, and even if the DB server is stopped and restarted.

      This is a problem because it appears that the file has not changed, so utilities like rsync are fooled into not backing up the file.

      Problem occurs on:

      • Linux Fedora Core 8, running on AWS EC2 32-bit server.
      • Linux Fedora 13, running on AWS EC2 64-bit server.

      Works fine (timestamp IS updated) on Mac OS X 10.6.5 (Snow Leopard)

      --Fred Stluka

            Assignee:
            mathias@mongodb.com Mathias Stearn
            Reporter:
            fredstluka Fred Stluka
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: