I found a problematic issue in 9.0, and I'm going to retire this version. I will release shortly a new 9.1 fixing the issue.
If you have already upgraded to 9.0, just avoid to sync for now.
If you sync anyway, it's possible that SnapRAID 9.0 won't be able to read the content file. If you get stuck in this condition, just do nothing. Your content file is OK, and data is protected.
It's just SnapRAID 9.0 not able to read it. As soon 9.1 is released, you can replace the SnapRAID executable, and continue from this point.
Or, if you prefere, you also have the alternative to downgrade to 8.1. It's expected to work. But it's not verified.
Ciao,
Andrea
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Although this sounds scary at first, when you read that the content file is okay and our data is protected, the fear quickly evaporates. Will this shortly available fix be in hours or take a few days? Thanks again for your hard work, and for reporting this instead of just glossing over it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"OUTERR] Error reopening the content file 'C:/SnapRAID/SnapRAID.content.tmp'. No such file or directory [2/2].
2015-11-19 14:52:57,348 [ERROR ] Command 'snapraid sync' returned non-zero exit status 1"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I found a problematic issue in 9.0, and I'm going to retire this version. I will release shortly a new 9.1 fixing the issue.
If you have already upgraded to 9.0, just avoid to sync for now.
If you sync anyway, it's possible that SnapRAID 9.0 won't be able to read the content file. If you get stuck in this condition, just do nothing. Your content file is OK, and data is protected.
It's just SnapRAID 9.0 not able to read it. As soon 9.1 is released, you can replace the SnapRAID executable, and continue from this point.
Or, if you prefere, you also have the alternative to downgrade to 8.1. It's expected to work. But it's not verified.
Ciao,
Andrea
Although this sounds scary at first, when you read that the content file is okay and our data is protected, the fear quickly evaporates. Will this shortly available fix be in hours or take a few days? Thanks again for your hard work, and for reporting this instead of just glossing over it.
Hi rubylaser,
I expect to release 9.1 tomorrow.
Ciao,
Andrea
This error?
"OUTERR] Error reopening the content file 'C:/SnapRAID/SnapRAID.content.tmp'. No such file or directory [2/2].
2015-11-19 14:52:57,348 [ERROR ] Command 'snapraid sync' returned non-zero exit status 1"
Hi Sunday,
What version reported this error ?
Ciao,
Andrea
Version 9.0. Previous and subsequent syncs seemed to have completed without error though.
Thanks Sunday,
Yes. There was a data race on the file name in Windows, that could possibly result in this effect. Running again the command fixes it.
Ciao,
Andrea