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

wt "backup" command fails when run against a mongod with wiredTiger storage engine's dbpath

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage, WiredTiger
    • Storage Execution
    • Fully Compatible
    • ALL

      to repro:

      1) start up a mongod with --storageEngine=wiredTiger
      2) insert some data
      3) shut it down.
      4) use the "wt" command to try to generate a backup:

      ./wt -C "extensions=[./ext/compressors/snappy/.libs/libwiredtiger_snappy.so]" -h /data/db/copied_path2/ backup /tmp
      lt-wt: /data/db/copied_path2//WiredTigerLog.0000000011: No such file or directory
      

      The file that it looks for is actually in journal/ within the specified path, but the WT command won't look in there. It still won't work even when trying to specifically point it to journal/ :

      $ ./wt -C "extensions=[./ext/compressors/snappy/.libs/libwiredtiger_snappy.so],log=(path=journal)" -h /data/db/copied_path2 backup /tmp/
      lt-wt: /data/db/copied_path2/WiredTigerLog.0000000015: No such file or directory
      
      $ ./wt -C "extensions=[./ext/compressors/snappy/.libs/libwiredtiger_snappy.so]" -h /data/db/copied_path2/journal backup /tmp/
      [1421186937:53197][11490:0x7f308da78740], wiredtiger_open: /data/db/copied_path2/journal/WiredTiger: No such file or directory
      lt-wt: No such file or directory
      

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            mikeo@mongodb.com Michael O'Brien
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: