Skip to content

Commit

Permalink
Workaround copying file returning EAGAIN on ZFS on mac OS
Browse files Browse the repository at this point in the history
Falling back to hard_link when that happens, retrying can lead to very
long wait before copying works (up to 4secs in my tests) while
hard_linking works straight away.

Looks related to openzfsonosx/zfs#809

Closes rust-lang#13838
  • Loading branch information
thiblahute committed May 2, 2024
1 parent d34d0a1 commit 689fe2a
Showing 1 changed file with 17 additions and 1 deletion.
18 changes: 17 additions & 1 deletion crates/cargo-util/src/paths.rs
Original file line number Diff line number Diff line change
Expand Up @@ -585,7 +585,23 @@ fn _link_or_copy(src: &Path, dst: &Path) -> Result<()> {
// Note that: fs::copy on macos is using CopyOnWrite (syscall fclonefileat) which should be
// as fast as hardlinking.
// See https://github.com/rust-lang/cargo/issues/10060 for the details
fs::copy(src, dst).map(|_| ())
fs::copy(src, dst).map_or_else(
|e| {
if e.raw_os_error()
.map_or(false, |os_err| os_err == libc::EAGAIN)
{
tracing::info!("copy failed {e:?}. falling back to fs::hard_link");

// Working around an issue copying too fast with zfs (probably related to
// https://github.com/openzfsonosx/zfs/issues/809)
// See https://github.com/rust-lang/cargo/issues/13838
fs::hard_link(src, dst)
} else {
Err(e)
}
},
|_| Ok(()),
)
} else {
fs::hard_link(src, dst)
}
Expand Down

0 comments on commit 689fe2a

Please sign in to comment.