从 Subversion 损坏中恢复
subversion 中出了问题，现在
svnadmin: Invalid diff stream: [tgt] insn 0 starts beyond the target view position
如果我尝试从存储库进行转储，我将面临问题。 我们在这里还有另一个问题 Subversion 存储库错误，但那里的解决方案对我来说不够好，因为腐败是 85 次修订。
因为损坏位于一个不太重要的目录中（不在主干/分支/标签中），所以我正在考虑两种解决方案：
- 从健康部分创建转储，并将其导入到新存储库后提交与重要目录的差异（丢失所有修订历史记录）
- 从健康部分创建转储并编写一个 ruby 脚本来检查旧存储库中所需目录的每个修订。 这将创建一个用于修订的 diff 文件，并将其提交到带有作者姓名和原始评论的新存储库。
任何意见？ :)
/JaanusSiim
Something has gone wrong in subversion and now I am facing
svnadmin: Invalid diff stream: [tgt] insn 0 starts beyond the target view position
if I try to make dump from repository. We have another question about it here Subversion Repository Error, but the solutions there are not good enough for me because the corruption is 85 revisions back.
Because the corruption is in one not so important directory (not in trunk/branches/tags) I was thinking about two solutions:
- Create a dump from healthy portion and after importing it to new repository commit diffs from important directories (losing all revision history)
- Create a dump from healthy portion and write a ruby script that would check every revision of needed directories in old repository. This will create a diff file for revision and commit it to new repository with authors name and original comment.
Any comments? :)
/JaanusSiim
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您确实需要访问您的来源，我建议您发送邮件至 [email protected]< /a> 解决你的问题。 有些阅读该列表的用户拥有恢复损坏的存储库的经验。 （在许多情况下，它没有在列表中报告，因为恢复源代码通常需要 NDA）
创建您可以访问的所有有效修订版本的转储文件不会造成损害，并且可能有助于恢复。
If you really need access to your sources I would recommend sending a mail to [email protected] with your problem. There are some users reading that list that have experience in recovering corrupt repositories. (In many cases it wasn't reported on list as recovering sourcecode commonly requires a NDA)
Creating a dumpfile of all valid revisions you can get access to won't harm and might help in recovering.