You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 18, 2022. It is now read-only.
After some testing in 0.4.3, 0.5.0 and 0.5.0-rc2 and following the video commands and documentation commands, we have been unable to restore our changes to the volume after taking snapshots.
Our setup for testing:
Amazon Linux 2016.9
docker 1.12.1 build 23cf638
convoy (various versions)
AWS gp1 100GB separate volume for convoy
We have followed the commands to the letter from the video on the main page as well as the commands under the "Create a volume", "Create a snapshot of a volume", "Backup a volume" and "restore a volume" headings of the readme.md file to no avail.
The volume was partitioned by the dm_dev_partition.sh script. Also, we had to zero out the metadata partition using the dd command before we could get the convoy daemon to run.
The text was updated successfully, but these errors were encountered:
After some testing in 0.4.3, 0.5.0 and 0.5.0-rc2 and following the video commands and documentation commands, we have been unable to restore our changes to the volume after taking snapshots.
Our setup for testing:
Amazon Linux 2016.9
docker 1.12.1 build 23cf638
convoy (various versions)
AWS gp1 100GB separate volume for convoy
We have followed the commands to the letter from the video on the main page as well as the commands under the "Create a volume", "Create a snapshot of a volume", "Backup a volume" and "restore a volume" headings of the readme.md file to no avail.
The volume was partitioned by the dm_dev_partition.sh script. Also, we had to zero out the metadata partition using the dd command before we could get the convoy daemon to run.
The text was updated successfully, but these errors were encountered: