• [6.9.0 RC2] Mover file does not exist


    SiNtEnEl
    • Solved Minor

    When swapping my cache drive for a new one, i encountered a issue when moving data off my cache disk to the array with the mover.
    Lot of files did not get moved by the mover due a "does not exist" notice and No such file or directory.

    Workaround:
    I had to move the files manually in the terminal. Files where not locked, neither where there permission issues.

    Example:

    /mnt/user/appdata/linuxserver-plex/Library/Application Support/Plex Media Server/Metadata/TV Shows/8/145fa310d3a3602fe884933af4b1bb329951e0a.bundle/Contents/com.plexapp.agents.thetvdb/seasons/2/posters/d08056a72b0fb9cf1c627be9efe8d0bd1db65595

     

    Moving from /mnt/cache to /mnt/disk2/ resulted in this logging:


    Jan 11 18:19:34 UnNASty root: Specified filename /mnt/disk2/appdata/linuxserver-plex/Library/Application Support/Plex Media Server/Metadata/TV Shows/8/145fa310d3a3602fe884933af4b1bb329951e0a.bundle/Contents/_combined/seasons/2/posters/com.plexapp.agents.thetvdb_d08056a72b0fb9cf1c627be9efe8d0bd1db65595 does not exist.

    Jan 11 18:19:34 UnNASty move: move_object: /mnt/disk2/appdata/linuxserver-plex/Library/Application Support/Plex Media Server/Metadata/TV Shows/8/145fa310d3a3602fe884933af4b1bb329951e0a.bundle/Contents/_combined/seasons/2/posters/com.plexapp.agents.thetvdb_d08056a72b0fb9cf1c627be9efe8d0bd1db65595 No such file or directory

    No further logging found.

    This happend to most files of my appdata plex docker container.
    My guess it has to do with the length of the path?

    • Upvote 2



    User Feedback

    Recommended Comments



    Same here in 6.90 stable.

    Using unBalance/rsync to move currently.

    Not sure if this is new or old... I don't usually move my appdata except for needing to format cache for the 1MiB realignment and hence mover involvement.

    Array is XFS and cache is BTRFS. The filenames and paths shouldn't be the limiting factor unless mover can't handle the arguments for some reason is my thought....

    Link to comment

    I'm having the same issue with Plex files on 6.9.1 

    How are you using unBalance/rsync to move the files off of the cache? I have unbalanced installed, but only see the main array drives. I'm trying to replace a cache drive but can't clear out my cache drive.

    Link to comment
    5 minutes ago, tri.ler said:

    I'm having the same issue with Plex files on 6.9.1 

    How are you using unBalance/rsync to move the files off of the cache? I have unbalanced installed, but only see the main array drives. I'm trying to replace a cache drive but can't clear out my cache drive.

    With the array started, go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

    Link to comment

    I ended up just deleting the files since it seems to be just metadata that I assume plex can easily rebuild. I had to finish the cache drive swap today, but would still appreciate if anyone knows a fix in case it happens in the future. 

    Link to comment

    Sorry I'm late getting back. I just used unBalance and moved on!

    unBalance shows my cache drive and allows me to move to/from it without issues, so not sure why yours is missing it @tri.ler

    Seeing that both of us had this problem with the same plex metadata files, I think it must be a mover issue.

    @trurl I didn't see anything in my logs either, other than the file not found/no such file or directory errors. My file system was good. I'm happy to try and let mover give it another go to try to reproduce, but to what end if that is the only error?

    Let me know if I can help test any hypotheses...

    Link to comment

    Same problem for me with unraid 6.9.2 while moving the appdata of my plex docker container to the cache 

    Link to comment

    I can confirm that that I have the same problem.

    Just replaced my cache drive. 

     

    Unraid 6.9.2

    Mover Tuning 2021.05.13

    Of course VM and docker are turned off and I even reboot several times. 

    It seems cannot properly move XXYYZZ.bundle in /appdata/plex/Library/Application Support/Plex Media Server/Metadata/...

    The log says 'No such file or directory'.

    I think it might be the folder name or file name .bundle confused the Mover plug in.

     

    Thanks!

    Link to comment

    Hi same for me and also all docker files like this with 64 characters folders

     

    /mnt/cache/system/docker/btrfs/subvolumes/eebbee589230fdb1e25977336b1b28e529658a15a82f4b7ccf4ccbfb46834a7d/

     

    seems to be only symlinks

     

    ls -l /mnt/cache/system/docker/btrfs/subvolumes/eebbee589230fdb1e25977336b1b28e529658a15a82f4b7ccf4ccbfb46834a7d/bin/
    total 48
    lrwxrwxrwx 1 root root  4 Feb 10  2019 lsmod -> kmod
    lrwxrwxrwx 1 root root 20 May 15 23:00 mt -> /etc/alternatives/mt
    lrwxrwxrwx 1 root root 20 May 15 23:00 nc -> /etc/alternatives/nc
    lrwxrwxrwx 1 root root 24 May 15 23:00 netcat -> /etc/alternatives/netcat
    lrwxrwxrwx 1 root root  8 Sep 27  2018 nisdomainname -> hostname
    lrwxrwxrwx 1 root root  4 Mar  8 20:46 ping4 -> ping
    lrwxrwxrwx 1 root root  4 Mar  8 20:46 ping6 -> ping
    lrwxrwxrwx 1 root root  4 Apr 18  2019 rbash -> bash
    lrwxrwxrwx 1 root root  4 Jun 12  2019 rnano -> nano
    lrwxrwxrwx 1 root root  4 Aug  3  2020 sh -> dash
    lrwxrwxrwx 1 root root 20 Mar 18 20:59 systemd -> /lib/systemd/systemd
    lrwxrwxrwx 1 root root  8 Sep 27  2018 ypdomainname -> hostname

    Edited by Meldrak
    more details
    Link to comment
    On 5/24/2021 at 11:44 PM, jena said:

    the Mover plug in

    If any of you on this thread are using a plugin for mover you need to remove that plugin and see what happens with the builtin mover.

    Link to comment

    I just encountered this problem. I went to add a cache drive to my existing single SSD pool, to make it a dual SSD redundant one with mirroring. When I added the second SSD it warned that data on it would be formatted. I have read of other threads where the entire pool's contents were formatted so decided to back up everything onto array. I faced the same issues as above. I used the unbalanced plugin to get past the issues. I seem to recall some of the paths/files did in fact exist, but mover could not find them but can't be sure.

     

    However, when I moved everything back to cache drive using mover again, I got the same errors and this time checked a few of the paths/files it was talking about to see if they truly did exist, and they didn't. So why would mover try to move files or folders that genuinely do not exist. A strange situation. I confess that I did not have the time to properly troubleshoot this and grab all logs but thought I would put it out there that this may need more investigation. it definitely seems to be the plex app data paths that get very deep and with long names sometimes with dots in them.

    Link to comment

    same problem for me.

     

    For those that have moved them manually/with a CA, did you just move from mnt/cache to mnt/disk#?

    • Like 1
    Link to comment

    I have the same issue. There are thousands of these files and all of the are exists on the location which saying "No such file..." on unraid 6.9.2

     

    Nov 21 04:01:13 Pandora-NAS root: Specified filename /mnt/disk1/appdata/Plex-Media-Server/Library/Application Support/Plex Media Server/Metadata/TV Shows/e/31721686c60b228ff0a6a436b5f10e3a0244fdc.bundle/Contents/_combined/themes/com.plexapp.agents.plexthememusic_3ef0ef6f1f2088d165b2a9c69a7ec06eb19cfc08 does not exist.
    Nov 21 04:01:13 Pandora-NAS move: move: file /mnt/disk1/appdata/Plex-Media-Server/Library/Application Support/Plex Media Server/Metadata/TV Shows/e/31721686c60b228ff0a6a436b5f10e3a0244fdc.bundle/Contents/_combined/themes/com.plexapp.agents.plexthememusic_3ef0ef6f1f2088d165b2a9c69a7ec06eb19cfc08
    Nov 21 04:01:13 Pandora-NAS move: move_object: /mnt/disk1/appdata/Plex-Media-Server/Library/Application Support/Plex Media Server/Metadata/TV Shows/e/31721686c60b228ff0a6a436b5f10e3a0244fdc.bundle/Contents/_combined/themes/com.plexapp.agents.plexthememusic_3ef0ef6f1f2088d165b2a9c69a7ec06eb19cfc08 No such file or directory


    For me it's a mover related issue and would be great if the support team could have a look

    Edited by monghuz
    added unraid version
    Link to comment

     I'm facing the same problem:

    982366391_2021-12-2713_19_22.thumb.png.2f430527d990495f571ec95a9d166eeb.png

     

    After enabling the logs it says these files do not exist:

    Dec 27 13:29:21 thoth root: Specified filename /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/cert.pem does not exist.
    Dec 27 13:29:21 thoth move: move: file /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/cert.pem [10301,c50fbc1c]
    Dec 27 13:29:21 thoth move: move_object: /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/cert.pem No such file or directory
    Dec 27 13:29:21 thoth root: Specified filename /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/chain.pem does not exist.
    Dec 27 13:29:21 thoth move: move: file /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/chain.pem [10301,c50fbc1d]
    Dec 27 13:29:21 thoth move: move_object: /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/chain.pem No such file or directory
    Dec 27 13:29:21 thoth root: Specified filename /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/fullchain.pem does not exist.
    Dec 27 13:29:21 thoth move: move: file /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/fullchain.pem [10301,c50fbc1e]
    Dec 27 13:29:21 thoth move: move_object: /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/fullchain.pem No such file or directory
    Dec 27 13:29:21 thoth root: Specified filename /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/privkey.pem does not exist.
    Dec 27 13:29:21 thoth move: move: file /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/privkey.pem [10301,c50fbc1f]
    Dec 27 13:29:21 thoth move: move_object: /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/privkey.pem No such file or directory

     

    But I have a different dir which contains links, which were moved:

    1659437646_2021-12-2713_24_26.png.6673690c8f5b82bd751ff157599ccd26.png

     

    The red color means that the symlinks target does not exist. This means the mover already moved the target file. Maybe the mover has a bug which fails because of that?

     

    There are other commands in Linux which fail with the same error:

    getfattr --dump /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/*
    getfattr: /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/cert.pem: No such file or directory
    getfattr: /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/chain.pem: No such file or directory
    getfattr: /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/fullchain.pem: No such file or directory
    getfattr: /mnt/cache/Backups/Shares/appdata/20211224_044001/npm/letsencrypt/live/npm-7/privkey.pem: No such file or directory

     

    getfattr needs an additional flag to check the symlink itself:

    -h, --no-dereference
    Do not dereference symlinks. Instead of the file a symlink refers to, the symlink itself is examined. Unless doing a logical (-L) traversal, do not traverse symlinks to directories.

     

    Is it possible that the Unraid Mover uses this command or a similar one?

     

    EDIT1: Yes, that is the problem. Because if I copy the symlink target files back to the cache, the mover now moves the symlinks to the array (but skips the duplicated files, which is an expected behavior).

     

    EDIT2: One "bug" is this "fuser" command in file /usr/local/sbin/in_use:

    fuser -s "$FILE" && exit

     

    fuser fails if the file does not exist, and as it follows symlinks, it does fail:

     

    image.png.5313ef9a2010a8f56424b3a4bc9d572f.png

     

    So Limetech should use something like this instead, to avoid in-use checks for symlinks as symlinks can't be in-use at all:

    [[ -L "$FILE" ]] && exit 1

     

     

    • Like 2
    Link to comment

    Hi @mgutt,

     

    Thanks for sharing the result of your investigation.

    I'm new on this forum so I'm not sure how to engange engange the owners of unraid to get their feedback. 

     

    Regarding your below note is this command that we can use it as a workaround to fix the issue? e.g. to recreate the symlinks?

    On 12/27/2021 at 1:49 PM, mgutt said:

    Internal note:

    rsync --archive --itemize-changes --ignore-existing --remove-source-files /mnt/cache/Backups/Shares/appdata/ /mnt/disk7/Backups/Shares/appdata && rsync --archive --itemize-changes --delete "$(mktemp -d)/" /mnt/cache/Backups/Shares/appdata/

     

    Thanks,

    monghuz

     

    Link to comment

    Well, I had the same thing happen to me today. After moving all files to the array there was about 3,5GB remaining. Looking at the cache drive there were the following folders present:

    - swag/etc/letsencrypt

    - binhex-krusader

     

    swag listed the same 4 files mentioned in an earlier post. 

    binhex-krusader listed a folder with icons.

     

    Mover said files weren't there. Going to /mnt/cache/... nothing was there. Only folders. 

     

    Eventually switched out the drives and moved everything back. Unfortunately Swag wouldn't work. All sorts of errors in the log referring to the files that weren't moved. So I had to replace all the data with a backup from yesterday. In the middle of doing just that. 

     

    Hope this issue gets some love. Because the step to use mover is essentially worthless now. Just change out the drives and do a restore. Much faster that way. 

     

    Link to comment

    +1 Same issue with these Plex and Swag files and mover saying No such file or directory, 6.9.2. What's the fix here?

    Edited by norp90
    Link to comment

    This bug seems to be present for a long time:

     

     

     

     

     

    On 4/9/2022 at 3:29 PM, bonienl said:

    When using Unraid 6.10-rc3 or later, you can use the Dynamix File Manager to move files around.

     

    For me its a daily situation (backups) when symlinks are created. So a manually move is not practical.

    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.