Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: extend snapshot copy to filesystems that cannot link (#22703) #22730

Merged
merged 1 commit into from
Oct 21, 2021

Conversation

davidby-influx
Copy link
Contributor

If os.Link fails with syscall.ENOTSUP, then the file
system does not support links, and we must make copies
to snapshot files for backup. We also automatically make
copies instead of link on Windows, because although it
makes links, their semantics are different from Linux.

closes #16739

(cherry picked from commit d9b9e86)

closes #22700

If os.Link fails with syscall.ENOTSUP, then the file
system does not support links, and we must make copies
to snapshot files for backup. We also automatically make
copies instead of link on Windows, because although it
makes links, their semantics are different from Linux.

closes #16739

(cherry picked from commit d9b9e86)

closes #22700
Copy link
Contributor

@williamhbaker williamhbaker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@davidby-influx davidby-influx merged commit effd948 into 1.9 Oct 21, 2021
@davidby-influx davidby-influx deleted the DSB_copy_link_1.9 branch October 21, 2021 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Backup failure: Download shard n failed copy backup to file [Port to 1.9]
2 participants