Rsync shows files being copied, but the destination directory doesn't have the files












0















I put a new drive in my NAS(Freenas) and need to copy the contents from another drive.
I'm signed in as root via SSH. I've been using the command rsync -avP /mnt/Red3TB/Temp/Videos/ /mnt/Red4TB/Temp/Vidoes



The screen shows files being copied successfully, but when I go to the destination folder in the mapped shared drive in Windows and as root in Putty there are no files there. If I run Rsync again, it starts at the same 1st file. So, I know the files aren't being copied. If they were Rsync would start after the most recent file that was on both source and destination.



I did notice it would say this after I hit Ctrl-C to stop the Rsync



rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(642) 
[sender=3.1.3]
rsync: mkstemp "/mnt/Red4TB/Temp/Videos/FILENAME_HERE.2Gs8hT" failed:
Operation not permitted (1)









share|improve this question





























    0















    I put a new drive in my NAS(Freenas) and need to copy the contents from another drive.
    I'm signed in as root via SSH. I've been using the command rsync -avP /mnt/Red3TB/Temp/Videos/ /mnt/Red4TB/Temp/Vidoes



    The screen shows files being copied successfully, but when I go to the destination folder in the mapped shared drive in Windows and as root in Putty there are no files there. If I run Rsync again, it starts at the same 1st file. So, I know the files aren't being copied. If they were Rsync would start after the most recent file that was on both source and destination.



    I did notice it would say this after I hit Ctrl-C to stop the Rsync



    rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(642) 
    [sender=3.1.3]
    rsync: mkstemp "/mnt/Red4TB/Temp/Videos/FILENAME_HERE.2Gs8hT" failed:
    Operation not permitted (1)









    share|improve this question



























      0












      0








      0








      I put a new drive in my NAS(Freenas) and need to copy the contents from another drive.
      I'm signed in as root via SSH. I've been using the command rsync -avP /mnt/Red3TB/Temp/Videos/ /mnt/Red4TB/Temp/Vidoes



      The screen shows files being copied successfully, but when I go to the destination folder in the mapped shared drive in Windows and as root in Putty there are no files there. If I run Rsync again, it starts at the same 1st file. So, I know the files aren't being copied. If they were Rsync would start after the most recent file that was on both source and destination.



      I did notice it would say this after I hit Ctrl-C to stop the Rsync



      rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(642) 
      [sender=3.1.3]
      rsync: mkstemp "/mnt/Red4TB/Temp/Videos/FILENAME_HERE.2Gs8hT" failed:
      Operation not permitted (1)









      share|improve this question
















      I put a new drive in my NAS(Freenas) and need to copy the contents from another drive.
      I'm signed in as root via SSH. I've been using the command rsync -avP /mnt/Red3TB/Temp/Videos/ /mnt/Red4TB/Temp/Vidoes



      The screen shows files being copied successfully, but when I go to the destination folder in the mapped shared drive in Windows and as root in Putty there are no files there. If I run Rsync again, it starts at the same 1st file. So, I know the files aren't being copied. If they were Rsync would start after the most recent file that was on both source and destination.



      I did notice it would say this after I hit Ctrl-C to stop the Rsync



      rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(642) 
      [sender=3.1.3]
      rsync: mkstemp "/mnt/Red4TB/Temp/Videos/FILENAME_HERE.2Gs8hT" failed:
      Operation not permitted (1)






      rsync freenas






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 18 at 4:05







      Craig B

















      asked Jan 18 at 3:50









      Craig BCraig B

      112




      112






















          1 Answer
          1






          active

          oldest

          votes


















          1














          Looks like rysnc no longer works with windows datasets and you can't use the -p argument with them.
          These arguments should not be used.
          -a, --archive equals -rlptgoD (no -H, -A -X)
          -p, --perms Preserve permssions
          -A, --acls Preserve ACLs (implies -p)



          See here for full details and credit where I found the answer






          share|improve this answer



















          • 1





            What do you mean by Windows datasets? I would guess that the problem is caused by the Windows file system (NTFS, FAT32 or exFAT), where the file permissions cannot be treated individually, when opened in linux. Or is it caused by Windows style file names that are not compatible with linux file systems or something else?

            – sudodus
            Jan 18 at 7:51











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f495215%2frsync-shows-files-being-copied-but-the-destination-directory-doesnt-have-the-f%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          Looks like rysnc no longer works with windows datasets and you can't use the -p argument with them.
          These arguments should not be used.
          -a, --archive equals -rlptgoD (no -H, -A -X)
          -p, --perms Preserve permssions
          -A, --acls Preserve ACLs (implies -p)



          See here for full details and credit where I found the answer






          share|improve this answer



















          • 1





            What do you mean by Windows datasets? I would guess that the problem is caused by the Windows file system (NTFS, FAT32 or exFAT), where the file permissions cannot be treated individually, when opened in linux. Or is it caused by Windows style file names that are not compatible with linux file systems or something else?

            – sudodus
            Jan 18 at 7:51
















          1














          Looks like rysnc no longer works with windows datasets and you can't use the -p argument with them.
          These arguments should not be used.
          -a, --archive equals -rlptgoD (no -H, -A -X)
          -p, --perms Preserve permssions
          -A, --acls Preserve ACLs (implies -p)



          See here for full details and credit where I found the answer






          share|improve this answer



















          • 1





            What do you mean by Windows datasets? I would guess that the problem is caused by the Windows file system (NTFS, FAT32 or exFAT), where the file permissions cannot be treated individually, when opened in linux. Or is it caused by Windows style file names that are not compatible with linux file systems or something else?

            – sudodus
            Jan 18 at 7:51














          1












          1








          1







          Looks like rysnc no longer works with windows datasets and you can't use the -p argument with them.
          These arguments should not be used.
          -a, --archive equals -rlptgoD (no -H, -A -X)
          -p, --perms Preserve permssions
          -A, --acls Preserve ACLs (implies -p)



          See here for full details and credit where I found the answer






          share|improve this answer













          Looks like rysnc no longer works with windows datasets and you can't use the -p argument with them.
          These arguments should not be used.
          -a, --archive equals -rlptgoD (no -H, -A -X)
          -p, --perms Preserve permssions
          -A, --acls Preserve ACLs (implies -p)



          See here for full details and credit where I found the answer







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 18 at 4:31









          Craig BCraig B

          112




          112








          • 1





            What do you mean by Windows datasets? I would guess that the problem is caused by the Windows file system (NTFS, FAT32 or exFAT), where the file permissions cannot be treated individually, when opened in linux. Or is it caused by Windows style file names that are not compatible with linux file systems or something else?

            – sudodus
            Jan 18 at 7:51














          • 1





            What do you mean by Windows datasets? I would guess that the problem is caused by the Windows file system (NTFS, FAT32 or exFAT), where the file permissions cannot be treated individually, when opened in linux. Or is it caused by Windows style file names that are not compatible with linux file systems or something else?

            – sudodus
            Jan 18 at 7:51








          1




          1





          What do you mean by Windows datasets? I would guess that the problem is caused by the Windows file system (NTFS, FAT32 or exFAT), where the file permissions cannot be treated individually, when opened in linux. Or is it caused by Windows style file names that are not compatible with linux file systems or something else?

          – sudodus
          Jan 18 at 7:51





          What do you mean by Windows datasets? I would guess that the problem is caused by the Windows file system (NTFS, FAT32 or exFAT), where the file permissions cannot be treated individually, when opened in linux. Or is it caused by Windows style file names that are not compatible with linux file systems or something else?

          – sudodus
          Jan 18 at 7:51


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f495215%2frsync-shows-files-being-copied-but-the-destination-directory-doesnt-have-the-f%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          How to make a Squid Proxy server?

          第一次世界大戦

          Touch on Surface Book