Jump to content

  • 6.12.4 rysnc copied data sub folders not accessible

    Bushibot

    By Bushibot

      • Minor

    I'm seeing a issue that looks like a bug.

    • After I rsync data from my old nas or use Dynamix File Manager the sub folders are not accessible from the share via other computers (windows/ios/mac) all return a error when trying to access ONLY the sub folders. Top level folders/files seem to be fine.
    • Uraid can access the sub folders via file manger (everything looks normal), but containers can't.
    • My old Nas is mounted as SMB via Unassigned Devices.
    • If I remove that mount and copy direct via rsync (rsync -arhz --progress [email protected]:/mnt/HD/HD_a2/Public/sshkeys /mnt/user/datapool/) the same problem persists.

     

    Working

    • If I copy the data using a windows PC from one SMB mount to the other then everything works fine, sub folders and files are accessible (I need to move like 7T of data so that doesn't scale but is fine for testing).

     

    I'm new to unraid and no rsync export but this seems kind of broken. Noting magic about my setup. Happy to any data.

    I might try to rsync from the old nad but it's a pretty old busy box os not sure what I can do with it.

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    JorgeB

    Don't remember seeing this issue before, and never had issues using rsync myself, if you run the new permissions tool (Tools -> New permissions) after the copy does it start working?

     

    P.S. -r is not needed, it's included with -a, -z enables compression, this can actually slow down the transfer when done over LAN.

    Link to comment
    Bushibot
    11 hours ago, JorgeB said:

    Don't remember seeing this issue before, and never had issues using rsync myself, if you run the new permissions tool (Tools -> New permissions) after the copy does it start working?

     

    P.S. -r is not needed, it's included with -a, -z enables compression, this can actually slow down the transfer when done over LAN.

    Tried the permission tool on the share I might try on the whole disk, so far it didn't fix anything. it's not just rsync. FTP and SMB (unless from a windows host middlemaning).

    Link to comment
    Bushibot
    • Ran permission tool against all disks
    • then rsync test folder again
    • Same result see screen shot, no access only to sub folders top leve fine.

    rsync -arhz --progress [email protected]:/mnt/HD/HD_a2/Public/sshkeys /mnt/user/datapool/

     

    My sense is very much that there is some kind bit not being set, but I don't know how to dig deeper into the nix unraid side.

    image.thumb.png.db5acf97781002a1c2103a31c08c597d.png

    Link to comment
    Bushibot
    15 hours ago, JorgeB said:

    Don't remember seeing this issue before, and never had issues using rsync myself, if you run the new permissions tool (Tools -> New permissions) after the copy does it start working?

     

    P.S. -r is not needed, it's included with -a, -z enables compression, this can actually slow down the transfer when done over LAN.

    Also tried without compressing but that doesn't fix the issue, but good performance tip, thanks.

    Link to comment
    JorgeB

    Many users use rsync without any issues, including myself daily, can you test accessing the files from another computer/OS? An Ubuntu boot flash drive will do. If the same try rsync some files from you desktop to see if that produces a different result. 

    Link to comment
    dlandon

    My gut feel is you do not have file permission issues, but something else affecting your user access.  Possibly user permissions?

     

    I'm seeing some issues with your server that may or may not be affecting your issue: 

    Sep  7 10:40:42 nas-mass kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep  7 10:40:42 nas-mass kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep  7 10:40:42 nas-mass kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep  7 10:40:42 nas-mass kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep  7 10:40:42 nas-mass kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

    Some disks not running a 6Gbps.

     

    BIOS issues: 

    Sep  7 10:40:42 nas-mass kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT3._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330)
Sep  7 10:40:42 nas-mass kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT3._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep  7 10:40:42 nas-mass kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330)
Sep  7 10:40:42 nas-mass kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep  7 10:40:42 nas-mass kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330)
Sep  7 10:40:42 nas-mass kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep  7 10:40:42 nas-mass kernel: ata4.00: supports DRM functions and may not be fully accessible
Sep  7 10:40:42 nas-mass kernel: ata4.00: ATA-9: HGST HUS728T8TALE6L1, V8GNX9G0, max UDMA/133
Sep  7 10:40:42 nas-mass kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330)
Sep  7 10:40:42 nas-mass kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep  7 10:40:42 nas-mass kernel: ata3.00: supports DRM functions and may not be fully accessible
Sep  7 10:40:42 nas-mass kernel: ata3.00: ATA-9: HGST HUS728T8TALE6L1, V8GNX9G0, max UDMA/133
Sep  7 10:40:42 nas-mass kernel: ata6.00: supports DRM functions and may not be fully accessible
Sep  7 10:40:42 nas-mass kernel: ata6.00: ATA-9: HGST HUS728T8TALE6L1, V8GNX9G0, max UDMA/133
Sep  7 10:40:42 nas-mass kernel: ata2.00: supports DRM functions and may not be fully accessible
Sep  7 10:40:42 nas-mass kernel: ata2.00: ATA-11: Samsung SSD 870 QVO 2TB, SVQ02B6Q, max UDMA/133
Sep  7 10:40:42 nas-mass kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-330)
Sep  7 10:40:42 nas-mass kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)

     

    I don't know what all this means, but until this is sorted out so we know it is not affecting your issue, we probably can't offer much more help.

     

    You have a Realtek NIC and they are notoriously troublesome on Linux because the drivers are not actively maintained; 

    Sep  7 10:40:42 nas-mass kernel: RTL8211E Gigabit Ethernet r8169-0-300:00: attached PHY driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC)

     

    Link to comment
    Bushibot

    I’m not sure what I can do about any of those issues. It’s a Assus p8Z77-v mother board. So hardware is what is. Network seems to be fine etc. I can google a few but bios has been up to date for years.

     

    Nine that would explain ownership or permission issuers though, that is all OS side.. If I was having a performance issue, sure, potentially relevant, but there is not even cursory correlation there. 

    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.

×
×
  • Create New...