Title: shutil.move fails to move symlink (Invalid cross-device link)
Type: behavior Stage:
Components: Library (Lib) Versions: Python 3.6, Python 3.5, Python 2.7
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: Jeffrey.Kintscher, Murray Wilson, Unode, tarek
Priority: normal Keywords:

Created on 2016-04-17 16:58 by Unode, last changed 2020-07-31 18:02 by SilentGhost.

Messages (4)
msg263616 - (view) Author: Renato Alves (Unode) Date: 2016-04-17 16:58
Hi everyone,

I'm not really sure if this is a new issue but digging through the bug reports from the past I couldn't find an answer.
There's but this seems to be a different issue.
I also found that addressed problems with symlinks but didn't correct the behavior reported here.

The problem can be visualized with the following code.
Code fails on python 2.7 as well as python 3.4+. Not tested in python <2.7 and <3.4.

    import shutil
    import os
    TMPDIR = "/tmp/tmpdir"
    TESTLINK = "test_dir"
    if not os.path.isdir(TMPDIR):
    if not os.path.islink(TESTLINK):
        os.symlink(TMPDIR, TESTLINK)
    shutil.move(TESTLINK, TMPDIR)

When executed it gives me:

    % python3
    Traceback (most recent call last):
      File "", line 14, in <module>
        shutil.move(TESTLINK, TMPDIR)
      File "/usr/lib64/python3.4/", line 516, in move
        os.rename(src, dst)
    OSError: [Errno 18] Invalid cross-device link: 'test_dir' -> '/tmp/tmpdir'

This happens because /tmp is:

  tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,nodiratime)

In the past the recommendation to handle this problem was to stop using os.rename and use shutil.move instead.
This was even discussed in a bug report -

If one searches for this exception there's plenty of advice [1][2][3][4] in the same direction.
However, given that shutil.move uses os.rename internally, the problem returns.

On the other end doing the equivalent action in the shell with 'mv' works fine.

[1] -
[2] -
[3] -
[4] -
msg263617 - (view) Author: Renato Alves (Unode) Date: 2016-04-17 17:01
Also related to
msg263654 - (view) Author: SilentGhost (SilentGhost) * (Python triager) Date: 2016-04-18 08:09
This seems to be only triggered when moving a symlink into its destination. Assumption in the code is that when _samefile returns True, it must be due to case-insensitive filesystem, rather than this edge case.
msg374648 - (view) Author: Murray Wilson (Murray Wilson) Date: 2020-07-31 17:22
It also happens when moving a file in linux from an xfs filesystem to a NFS mounted filesystem.
Date User Action Args
2020-07-31 18:02:55SilentGhostsetnosy: - SilentGhost
2020-07-31 17:22:31Murray Wilsonsetnosy: + Murray Wilson
messages: + msg374648
2019-06-01 20:46:10Jeffrey.Kintschersetnosy: + Jeffrey.Kintscher
2016-04-18 08:09:08SilentGhostsetversions: + Python 3.6, - Python 3.4
nosy: + SilentGhost, tarek

messages: + msg263654

type: behavior
2016-04-17 17:01:21Unodesetmessages: + msg263617
2016-04-17 16:59:06Unodesetversions: + Python 2.7, Python 3.5
2016-04-17 16:58:17Unodecreate