Uploaded image for project: 'TrueNAS'
  1. TrueNAS
  2. NAS-108412

Cloud sync task fails before running pre-script if directory does not exist

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Engineering Closed (View Workflow)
    • Priority: Low
    • Resolution: Need additional information
    • Affects Version/s: 12.0-RELEASE
    • Fix Version/s: N/A
    • Component/s: Tasks
    • Impact:
      Low

      Description

      In my case, the pre-script only makes available the directory that is to be cloud-synced. More precisely, in the pre-script I shut down the running service whose data is to be synced to ensure data consistency, take a snapshot, and then spin it back up to minimize downtime. I then run cloud sync on the snapshot directory in the special-purpose .zfs/snapshot/<snapshotname> subdirectory. (and delete the snapshot in the post-script).

       

      There are some (dirty) ways to work around this, e.g. keep a snapshot alive to fake the directory so Cloud Sync doesn't complain, so I've marked the priority as low, but I still see it as a deficiency.

       

      Please consider only evaluating whether the directory exists after running the pre-script (or add better native functionality for using snapshots as cloud sync data sources in PUSH mode!)

        Attachments

          Attachments

            JEditor

              Activity

                People

                Assignee:
                releng Triage Team
                Reporter:
                jfalke Johannes Falke
                Watchers:
                Bonnie Follweiler, Johannes Falke
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: