Jump to content

dlandon

Community Developer
  • Posts

    10,398
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by dlandon

  1. Different problem now. Please go to the UD page and click the '+' by the drive and show a screen shot.
  2. I've released an update that will now set user to 'nobody' on all UD SMB shares. This includes physical disks, remote shares, and iso mounts. This may help with some permission issues that have come up. The best I can tell, this won't create any problems with permissions as Unraid defaults to the user 'nobody'. The mount physical disk time out has been increased to three minutes. Lots of code cleanup. A lot of the procedures were written some time ago, and I have just now spent time re-writing the code to standard coding practices. For those of you using SSDs with UD, the 'discard' option is added to the mount command on file systems that support discard - xfs and btrfs. This includes encrypted disks. Reiserfs does not support discard. On my LAN I have set NetBIOS off and WDS on on my main server and backup server. I recommend doing this unless you have to have SMB1 for some older devices. You probably need to look at updating or replacing devices that only use SMB1. I have been noticing sometimes devices (including Unraid) cannot see another SMB device on the LAN. A reboot of the device that cannot see another will correct the problem. I'm also suspicious of the latest Windows 10 update (1909). There have been times my laptop could not access the login to Unraid because the server name could not be found. Again a quick reboot of the laptop fixes things. I think Microsoft and the Samba development team are still sorting out SMB issues. In the meantime, I'll do my best to keep up with fixing issues.
  3. The time outs were just recently added to all commands so UD would not get stuck.
  4. The mount command timed out after 60 seconds when trying to mount the device. I'm quite surprised it takes that long. Do the drives have to spin up when the Drobo is mounted? The timeouts on commands are to keep UD from potentially hanging up. I'm probably going to extend the time out on physical disk mounts.
  5. Check your Acronis credentials for access to the Unraid share used for backups. I set up a special user to do backups with Acronis. Using 'Admin' credentials caused problems for me. You need to set up r/w access for this user on Unraid. I think some changes in Samba lately have caused this issue.
  6. I should have been clearer. My issue is more of what Samba is doing to permissions and ownership and/or how Unraid is setting them through Samba.
  7. I'm closing this until I can better understand what is going on here. I think the issue is more my ignorance on how permissions and ownership work.
  8. The original post has permissions of 660 and ownership of admin:users. The login used to access the share for backups is 'home' not 'admin'. The permissions are 660, not 666 that would allow everyone access. The computer being backed up is accessing all shares using 'admin', but is using 'home' user for this backup share. You are suggesting this is the Acronis backup? How do you explain this? I haven't tested 6.7 as it is not possible for me to easily roll back, so I can't confirm it. Something has changed.
  9. It's my understanding that Unraid always sets permissions to nobody:users.
  10. I'm also seeing some strangeness with CIFS mounts. Mounting a remote share using CIFS setting the uid=99 and gid=100 should set permissions of nobody:users. /sbin/mount -t cifs -o rw,nounix,iocharset=utf8,_netdev,file_mode=0777,dir_mode=0777,uid=99,gid=100,,vers=3.0,credentials='/tmp/unassigned.devices/credentials' '//Mediaserver/Public' '/mnt/disks/Mediaserver_Public' When I create a file on the remote share the permissions are set to: /mnt/disks/Mediaserver_Public - this is the remote share mount point on the local server. -rwxrwxrwx 1 nobody users 0 Dec 17 16:21 test\ permissions.txt* /mnt/user/Public - this is the remote share on the remote server. -rw-rw-rw- 1 guest users 0 Dec 17 16:21 test\ permissions.txt Mounting a remote share using CIFS setting the uid='nobody' and gid='users' should set permissions of nobody:users. /sbin/mount -t cifs -o rw,nounix,iocharset=utf8,_netdev,file_mode=0777,dir_mode=0777,uid='nobody',gid='users',,vers=3.0,credentials='/tmp/unassigned.devices/credentials' '//Mediaserver/Public' '/mnt/disks/Mediaserver_Public' /mnt/disks/Mediaserver_Public - this is the remote share mount point on the local server. -rwxrwxrwx 1 nobody users 0 Dec 17 16:32 test\ permissions.txt* /mnt/user/Public - this is the remote share on the remote server. -rw-rw-rw- 1 admin users 0 Dec 17 16:32 test\ permissions.txt I would expect all permissions to be nobody:users in all cases.
  11. In case it makes a difference, I have NetBIOS disabled, and WSD enabled.
  12. The software is Acronis backup and I have been using it without seeing this issue for years. I have a special user that I use to login to the share with Acronis that only has permission to access the backup share.
  13. When I create a text file using Windows 10 on an SMB share the permissions are set to: -rw-rw-rw- 1 admin users 0 Dec 17 16:54 test\ permissions.txt Copying a file from one Unraid server to another: Source: -rw-rw-rw- 1 nobody users 18 Dec 17 17:12 test\ permissions.txt Destination: -rw-rw-rw- 1 admin users 18 Dec 17 17:12 test\ permissions.txt I am logged into the share using an 'admin' user.
  14. Files created through Samba shares are not setting permissions to nobody:users. total 393522636 -rw-rw-rw-+ 1 nobody users 33554432 Oct 26 19:03 D...r\ Backup_full_b103_s1_v1.tib -rw-rw-rw-+ 1 nobody users 41736957952 Oct 26 20:14 D...r\ Backup_full_b103_s1_v2.tib -rw-rw-rw-+ 1 nobody users 41968980480 Nov 3 20:31 D...r\ Backup_full_b104_s1_v1.tib -rw-rw-rw-+ 1 nobody users 41995778560 Nov 9 20:28 D...r\ Backup_full_b105_s1_v1.tib -rw-rw-rw-+ 1 nobody users 43247830016 Nov 17 20:18 D...r\ Backup_full_b106_s1_v1.tib -rw-rw-rw-+ 1 nobody users 43407541248 Nov 27 20:26 D...r\ Backup_full_b107_s1_v1.tib -rw-rw----+ 1 admin users 42760169984 Dec 3 20:24 D...r\ Backup_full_b108_s1_v1.tib -rw-rw----+ 1 admin users 42783333888 Dec 9 20:08 D...r\ Backup_full_b109_s1_v1.tib -rw-rw----+ 1 admin users 11609833472 Dec 15 19:19 D...r\ Backup_full_b110_s1_v1.tib -rw-rw----+ 1 admin users 30997140992 Dec 15 20:18 D...r\ Backup_full_b110_s1_v2.tib -rw-rw-rw-+ 1 nobody users 3581016576 Oct 27 19:07 D...r\ Backup_inc_b103_s2_v1.tib -rw-rw-rw-+ 1 nobody users 1225604096 Oct 28 19:03 D...r\ Backup_inc_b103_s3_v1.tib -rw-rw-rw-+ 1 nobody users 929987584 Oct 29 19:03 D...r\ Backup_inc_b103_s4_v1.tib -rw-rw-rw-+ 1 nobody users 1610059776 Oct 31 19:05 D...r\ Backup_inc_b103_s5_v1.tib -rw-rw-rw-+ 1 nobody users 1121332736 Nov 1 19:03 D...r\ Backup_inc_b103_s6_v1.tib -rw-rw-rw-+ 1 nobody users 1326885888 Nov 4 19:03 D...r\ Backup_inc_b104_s2_v1.tib -rw-rw-rw-+ 1 nobody users 1500738048 Nov 5 19:04 D...r\ Backup_inc_b104_s3_v1.tib -rw-rw-rw-+ 1 nobody users 706327040 Nov 6 19:02 D...r\ Backup_inc_b104_s4_v1.tib -rw-rw-rw-+ 1 nobody users 781005312 Nov 7 19:03 D...r\ Backup_inc_b104_s5_v1.tib -rw-rw-rw-+ 1 nobody users 1060108288 Nov 8 19:03 D...r\ Backup_inc_b104_s6_v1.tib -rw-rw-rw-+ 1 nobody users 3318227456 Nov 11 19:09 D...r\ Backup_inc_b105_s2_v1.tib -rw-rw-rw-+ 1 nobody users 1243727360 Nov 12 19:04 D...r\ Backup_inc_b105_s3_v1.tib -rw-rw-rw-+ 1 nobody users 3261709312 Nov 13 19:09 D...r\ Backup_inc_b105_s4_v1.tib -rw-rw-rw-+ 1 nobody users 1099701248 Nov 14 19:04 D...r\ Backup_inc_b105_s5_v1.tib -rw-rw-rw-+ 1 nobody users 1288908288 Nov 15 19:05 D...r\ Backup_inc_b105_s6_v1.tib -rw-rw-rw-+ 1 nobody users 5099088384 Nov 22 19:08 D...r\ Backup_inc_b106_s2_v1.tib -rw-rw-rw-+ 1 nobody users 4714370048 Nov 23 19:11 D...r\ Backup_inc_b106_s3_v1.tib -rw-rw-rw-+ 1 nobody users 2989081088 Nov 24 19:06 D...r\ Backup_inc_b106_s4_v1.tib -rw-rw-rw-+ 1 nobody users 1040195584 Nov 25 19:22 D...r\ Backup_inc_b106_s5_v1.tib -rw-rw-rw-+ 1 nobody users 1006299136 Nov 26 19:04 D...r\ Backup_inc_b106_s6_v1.tib -rw-rw-rw-+ 1 nobody users 1216510976 Nov 28 19:04 D...r\ Backup_inc_b107_s2_v1.tib -rw-rw-rw-+ 1 nobody users 621406720 Nov 29 19:03 D...r\ Backup_inc_b107_s3_v1.tib -rw-rw-rw-+ 1 nobody users 610340864 Nov 30 19:03 D...r\ Backup_inc_b107_s4_v1.tib -rw-rw----+ 1 admin users 2693766144 Dec 1 19:06 D...r\ Backup_inc_b107_s5_v1.tib -rw-rw----+ 1 admin users 685169664 Dec 2 19:04 D...r\ Backup_inc_b107_s6_v1.tib -rw-rw----+ 1 admin users 785208320 Dec 4 19:03 D...r\ Backup_inc_b108_s2_v1.tib -rw-rw----+ 1 admin users 1248407040 Dec 5 19:04 D...r\ Backup_inc_b108_s3_v1.tib -rw-rw----+ 1 admin users 954967040 Dec 6 19:03 D...r\ Backup_inc_b108_s4_v1.tib -rw-rw----+ 1 admin users 2576901632 Dec 7 21:16 D...r\ Backup_inc_b108_s5_v1.tib -rw-rw----+ 1 admin users 3027072512 Dec 8 19:07 D...r\ Backup_inc_b108_s6_v1.tib -rw-rw----+ 1 admin users 655553024 Dec 10 19:21 D...r\ Backup_inc_b109_s2_v1.tib -rw-rw----+ 1 admin users 2373876224 Dec 11 19:06 D...r\ Backup_inc_b109_s3_v1.tib -rw-rw----+ 1 admin users 3225392640 Dec 12 19:07 D...r\ Backup_inc_b109_s4_v1.tib -rw-rw----+ 1 admin users 621100544 Dec 13 20:08 D...r\ Backup_inc_b109_s5_v1.tib -rw-rw----+ 1 admin users 1618446848 Dec 14 19:06 D...r\ Backup_inc_b109_s6_v1.tib -rw-rwx---+ 1 admin users 607243776 Dec 16 19:04 D...r\ Backup_inc_b110_s2_v1.tib* This is causing issues with some applications.
×
×
  • Create New...