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.

Sign up for GitHub

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

Jump to bottom

`omc upgrade` fails with "invalid cross-device link" #192

Open

palonsoro opened this issue Jan 7, 2025 · 0 comments

palonsoro commented Jan 7, 2025 •

edited

Loading

On a system with the following characteristics:

Linux (Fedora 41) on x86-64
/tmp folder is on a different mount point than omc installation folder (omc is installed in ~/bin, /tmp is a tmpfs).

The following error happens:

rename /tmp/omcExecutable_3663917093.tmp /home/someuser/bin/omc: invalid cross-device link

As per what I could confirm with a quick strace, the os.Rename call used in #177 results on a renameat syscall in Linux:

424907 12:24:49.433105 renameat(AT_FDCWD</home/someuser>, "/tmp/omcExecutable_3663917093.tmp", AT_FDCWD</home/someuser>, "/home/someuser/bin/omc") = -1 EXDEV (Invalid cross-device link) <0.000016>

And as per what man renameat says, it is required that they are in the same mount point.

Not sure what would the best approach, maybe copying and deleting instead of renaming.

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment