frank-unr

Thanks! That should work. I didn't know about this newperms command.

I'm trying trying to fix permissions recursively to the standard unraid permissions at the end of a User Script but I can't figure out how. So far I have: chown -R nobody:users /mnt/user/backups-gdrive/ chmod -R u=rw,go=rw /mnt/user/backups-gdrive/ But I know that directories should also have +x. What would be the correct chmod command?

Thanks!

Bumping as I got this warning today. Should I be worried?

Thanks, Ok but files are owned by root now. So I would need to run a chown and chmod after rclone then to end up with nobody:users and correct permissions for files on shares? What do you mean by adjust the script parameters? rclone options?

I have a user script than run a rclone sync command. Files created have root only permissions. Is there any way to have the script run as nobody:users and create files with the correct permissions for files in the array?

For anyone reading this in the future: There is a rclone option that prevents the creation of zero size sparse files when there is Google drive error when you try to sync from Google drive to local unraid array. disable multi-thread downloads with --multi-thread-streams 0 stops sparse files from being created. For me the --local-no-sparse does not fix the problem https://rclone.org/docs/

df reports the same usage yeah. I made more sparse files so now the reported total size is 2.2TB root@Antec:~# df -h /dev/md7 Filesystem Size Used Avail Use% Mounted on /dev/md7 9.1T 2.2T 7.0T 24% /mnt/disk7 This is what the QDirStat docker shows when I look at folders that only contain those sparse files:

root@Antec:/dev# stat -f /dev/md7 File: "/dev/md7" ID: e508de7bfbef56ab Namelen: 255 Type: tmpfs Block size: 4096 Fundamental block size: 4096 Blocks: Total: 2048 Free: 2048 Available: 2048 Inodes: Total: 2028594 Free: 2027960 All drives give the same result...

I stumbled on a problem with how free disk space is presented by Unraid on the main tab. I recently added a new disk to my array. It appears as there is already 1.77 TB of data on it. However I know in reality there is much much less data. Using rclone I accidently created a bunch of "large" sparse files that use 0 bytes of storage. The actual size of all files on that drive is under 20 GB. On a smb share I see the sparse files as having size zero. Using ls -l I get 0 size for the sparse files. Using ls -s I get the large size that uses no actual disk space. From what I understand, this looks like a bug.

I'm not able to format a USB drive to exfat. It's a new drive. It had vfat on it. I was able to mount it with Unassigned Devices and see that it had some Manufacturer software on it. Next I clicked the red X for "Clear Disk" and that partition was deleted. Next I tried to format it to exfat. I end up with an empty partition. \ Edit: I was able to format to exFat in Windows. After I did that, I could mount it with Unassigned Devices. I tried again red X for "Clear Disk" and that partition was deleted. Next I tried to format it to exfat again and now it worked. Second Edit: Unassigned Devices does NOT LIKE the default Disk Label "USB_SanDisk_3.2Gen1" and this causes the problem somehow. If I change the Disk Label by changing the Mount Point to "USB250GB" now everything works and it can format to exfat.

Thanks. Somehow the problem fixed itself. Log used to stop with this line: 2022-01-12 11:49:43 Initialization Sequence Completed Now it continues.... 2022-01-12 11:50:00,044 DEBG 'start-script' stdout output: [info] Attempting to get external IP using 'http://checkip.amazonaws.com'... 2022-01-12 11:50:05,438 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address xxx.xxx.xxx.xxx and QBittorrent is only started later in the log.

I reverted to the previous version 4.3.9-2-01. Things looked ok when I did that. This morning I can't connect to the WebUI at all with a "This site can't be reached error" in Chrome. I restarted the Docker and that doesn't change anything. I'm not sure what caused this or what I should try next.

Just updated the docker to 4.4.0 and I have the exact same issues. In the WebUI, under the torrent list where the General / Trackers / Peers etc information is, everything was blank with 4.4.0 I reverted to the previous image (4.3.9-2-01) for now.

I understand, thanks. I'll leave it at that then. I have no idea what best practices are for files written inside a docker image. It just thought that the problem I ran into could potentially be avoided by default. Thank you very much for this Handbrake docker and the responsive and courteous support.