remotevisitor

Members
  • Posts

    412
  • Joined

  • Last visited

Everything posted by remotevisitor

  1. I think this is down to the way the mv (rename) interacts with the Use Cache setting. The Use Cache setting affects where new files are located. Now consider the case where one of your downloaders downloads a file which uses the Use Cache setting to place the file on the cache drive. All as expected. Now you run some program to move/rename the file to some other share. Now if possible Linux will just move the file to the destination on the same disk (which is not creating a new file but moving an existing one so the Use Cache setting has no effect) and only if that fails will it do a copy (which does create a new file so uses the Use Cache setting) and delete the original file. So if the file to be moved is on the cache disk in the downloads share it will end up still on the cache disk after it has been moved to a share which has Use Cache set to No ..... unexpected, but a feature on the way the system works.
  2. If you cannot open the files I don’t understand how you can copy them, as the copy process would need to open the files in order to do the copy. Are the original and the copy on the same data disk, or do they end up on different disks?
  3. As well as the file permissions (read/write/execute) what is owner/group of the problem files? Files copied via SMB will usually have the owner/group of nobody/users. It suspect the ones you copied might have the owner/group of root/root.
  4. See something call "Help" top right of your screenshot? Try clicking on that.
  5. But someone must still be using it as Microsoft pushed out an update this week, separate from their normal updates sequence, on all Windows still receiving updates, specifically for a serious vulnerability in Internet Explorer. Usually my work IT department allows us 7 to 10 days to apply updates before they force it onto the machines; In this case it was only 2 days. Can’t remember the last time I used Internet Explorer myself.
  6. No. Use either the "Include disks" option or "Exclude disks" option (whichever is more convenient), but don’t use both.
  7. While I guess this fix might be rolled into the next 6.7.3 release (now that it look like there will be one to fix the database corruption issues some people have be experiencing), for now if you have the latest CA Application auto update plugin installed it will automatically apply a fix.
  8. the following command will find any empty sub-directories, starting in the current directory: find . -type d -empty and the following on will find and delete any empty sub-directories, starting in the current directory: find . -type d -empty -delete
  9. All parity drives have to be equal or larger than the largest data drive. So your attempt to use the 4TB drive is not valid as you have a data drive which is 10TB. With 2 parity drives you are supposed to be able to recover from 2 failed drives, but if the configuration you are trying to create was allowed and the 2 10TB drives were to fail then you would not be able recover the failed 10TB data drive.
  10. Did you try enabling ‘reconstruct write’ mode (aka ‘turbo write’) to see if that improves your performance on your system?
  11. Is there any difference between the permissions/owner/group of the directory which has the problem files and one which does not? Does the directory name (and any parent directory names) have any special characters in them?
  12. I suspect much of what you have in your go file you should possibly move to running using the "User Scripts" plugin. That then helps to separate your customisations from the base Unraid.
  13. Haven’t tried it myself, but as already mentioned should be readable by virtually any Linux distribution, so install one in a VM on your windows system and mount the USB disk in the VM, then share it via SMB for access from your windows system. In fact, although Unraid is not officially supported in VMs it does work, so you could probably install a trial version of unRaid in a VM and then using the Unassigned Devices plugin to mount the USB disk and share it. This is definitely all something worth testing prior to any emergency with data you can afford to lose in case you do anything wrong.
  14. I would also suggest the plugin ‘Fix Common Problems’ is also highly recommended .... I suspect it would have flagged up your original problem with your cache settings. This plugin is excellent at flagging up common configuration issues and is continually improved as new issues are identified.
  15. Any bets that when you get the Diagnostics you will find that the cache has been set to ‘Prefer’ rather than ‘Yes’ so Unraid is trying to move files to the cache drive rather than from it?
  16. Due you have a cache drive? Is the share to which you are writing set to Cache Yes. What schedule do you have mover set to run? About your question on why read&write .... because when files are written to a parity protected disk a write operation actually requires a read from the parity and data disk + write to parity and data disk.
  17. Ok, so your problem is that when you copied the files off your original disk6 you accidentally copied them to a folder called disk6 on disk4. I you are ok using the command line then I would do the following: mv /mnt/disk4/disk6/* /mnt/disk4 rmdir /mnt/disk4/disk6 Otherwise you can do as Squid suggested. Update: Might be safer to do as Squid suggested as Krusader will probably successfully merge folder contents if a folder already exists when moving the files/folders from the disk6 folder.
  18. What is the output of the command: ls -d /mnt/disk*/disk6
  19. If I was doing this I would not bother writing the bulk transfer to the cache drive, but instead enable ‘turbo write’ (Settings -> Disk Settings -> Tuneable (md_write_method) -> reconstruct write) and then write to the shares under /mnt/user0 (by-passing the cache disk).
  20. Back on the 1st page on this thread Limetech on 5th June, said they are looking into this issue.
  21. The folder name must contain a character not valid in an SMB folder name so it is being displayed in a special 8 character shortened folder name.
  22. It it actually telling you that your log file system (which is held in RAM) is 99% full. This suggests you have some program producing lots of logging messages. ‘What is the output of the command: du -h /var/log
  23. If you are going to do this then you should use /mnt/user0/Emby rather than /mnt/user/Emby otherwise you will almost certainly end up with a load of zero length files if your are very careful/lucky. if any of those files you copied to the cache drive were already on the cache drive then they are now probably zero length.
  24. I also had the command fail when using the terminal window provided by the gui. However, if I used putty to ssh into the server the command worked ok.