January 5, 201115 yr Subject: cron: /usr/local/sbin/mover 2>&1 >/dev/null Message: Cannot stat file /proc/2429/fd/7: No such file or directory I have seen this several times over the last week or so. I don't see any log entries about this issue, but I do see a lot of 'duplicate object' log messages. This email came at 4:24 AM. It looks like it was at the end of the mover operation. My guess on the duplicate objects is that shfs is seeing the files on the cache drive and one of the unRaid disks while they are being moved and thinking the file is duplicated. Some of the files are several GBytes in size and would take a while to move. Does anyone have any idea what this email means? I'm not inclined to be concerned about it, but it does puzzle me. Should I be concerned?
January 5, 201115 yr They probably are, as you assumed, an artifact of a file being moved. The errors occur for everybody using a cache drive, it is just that hardly anybody has a working mail system defined that the "at" command can use for its output. You can ignore the mail. (and also the dupe-file notices) You should see how many I get whenever I run the script that evens out the movies on my drives according to alpha ranges. It sometimes runs for hours moving files from one disk to another.
January 5, 201115 yr Author Thanks Joe. I expected that the email was not important and the 'dupes' was just normal operation.
Archived
This topic is now archived and is closed to further replies.