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

Every 5 minutes mongod.exe wakes up an external drive

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 4.2.8
    • Component/s: None
    • None
    • ALL
    • Hide

      Run Process Monitor

      https://docs.microsoft.com/en-us/sysinternals/downloads/procmon

      Filter for Path that includes a drive Mongo isn't supposed to be using. You could also filter by process name mongod.exe. Wait briefly and it'll reveal the pattern of unwanted IO.

      Show
      Run Process Monitor https://docs.microsoft.com/en-us/sysinternals/downloads/procmon Filter for Path that includes a drive Mongo isn't supposed to be using. You could also filter by process name mongod.exe. Wait briefly and it'll reveal the pattern of unwanted IO.
    • Security 2020-12-14, Security 2020-12-28

      My local MongoDB server is installed to my S: drive where the configs and logs live.

      storage:
        dbPath: S:\MongoDB\data
      {{}}

      systemLog:
        destination: file
        logAppend: true
        path: S:\MongoDB\log\mongod.log

      IE: it has no reason to access any other drive however it I found something periodically accessing my P: drive which is an external USB disk. I noticed this because the external drive normally likes to sleep since it's mostly idle but the unwanted access would occasionally force the it to wake up noisily.

      Using Process Monitor I traced this to my mongod.exe process which appears to be querying disk space every 5 minutes:

      3:01:03.0012146 PM mongod.exe 21348 QuerySizeInformationVolume P:\ SUCCESS TotalAllocationUnits: 1,465,097,471, AvailableAllocationUnits: 233,436,301, SectorsPerAllocationUnit: 8, BytesPerSector: 512

      2:56:01.0028637 PM mongod.exe 21348 QuerySizeInformationVolume P:\ SUCCESS TotalAllocationUnits: 1,465,097,471, AvailableAllocationUnits: 233,436,301, SectorsPerAllocationUnit: 8, BytesPerSector: 512

      3:06:05.0016549 PM mongod.exe 21348 QuerySizeInformationVolume P:\ SUCCESS TotalAllocationUnits: 1,465,097,471, AvailableAllocationUnits: 233,436,301, SectorsPerAllocationUnit: 8, BytesPerSector: 512

       

      My first though was to disable the free cloud monitoring but this did not help. I scoured the manual page for the config and couldn't see anything either. I took a quick look through the git repository to try to see if I could trace back to where this was coming from but the trail went cold.

       

      I would be great if whatever this diagnostic was could be turned off so my system can save power and reduce wear by letting the drive spin down.

       

            Assignee:
            mark.benvenuto@mongodb.com Mark Benvenuto
            Reporter:
            glen.miner Glen Miner
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: