-
Unraid OS version 7.0.0 available
This happened to me on Unraid 6.12 with data directory + zfs pool. I already posted earlier in this thread but I am not sure this is resolved with overlay2. Docker official docs seem to say overlay2 + docker are not a match: https://docs.docker.com/engine/storage/drivers/select-storage-driver/#supported-backing-filesystems The UI in Unraid is also confusing as it offers native vs overlay2 but native says docker directory will use the supported file system (i.e. zfs). I'm stuck waiting on more official news but your note has me paused given it's the exact behavior I experienced (blocked web UI when docker download/unpacking was occurring, slow docker changes/apps, and docker operations causing lockups on docker apps).
-
ephservers started following Unraid OS version 7.0.0 available
-
Unraid OS version 7.0.0 available
I see the notes that if you're using data-dir for docker images and wanting to use a zfs pool as the target storage location that we should select overlay2. In the docker settings, I see that 'native' is one option and shows a zfs option for zfs-formatted file systems. Is there a reason overlay2 is better than the native/zfs option for zfs pools? I am not currently using a pool for my appdata and looking to gain some mirror data protection with a zpool. Thank you.
-
-
[6.11.5] Cache Pool files left stranded when moving between Shares on different pools
Originally posted on r/unraid but realized this is a better place. I stumbled on this today. Maybe someone here has seen this before? I found a way to get files stranded on a cache pool. My setup: 2 cache pools: One is named `app_data_cache` and it has a single share, `appdata` that has cache set to Prefer and assigned to the `app_data_cache` pool. One is named `cache` and has a share named `Backups` and has cache set to Yes and assigned to the `cache` pool. I was working with some Unraid files and I did the following commands: Check this folder and it does not have `Backups` in it: `root@Chonk:~# ls /mnt/app_data_cache/` `appdata/ system/` Checked to make sure no `hi.txt` exists: `root@Chonk:~# ls /mnt/user/Backups/hi.txt` `/bin/ls: cannot access '/mnt/user/Backups/hi.txt': No such file or directory` And no `/mnt/cache/Backups` `root@Chonk:~# ls /mnt/cache/Backups` `/bin/ls: cannot access '/mnt/cache/Backups': No such file or directory` Make a file: `root@Chonk:~# touch /mnt/user/appdata/hi.txt` File now exists: `root@Chonk:~# ls /mnt/app_data_cache/appdata/hi.txt ` `/mnt/app_data_cache/appdata/hi.txt` Move to another Share that happens to be on another cache pool: `root@Chonk:~# mv /mnt/user/appdata/hi.txt /mnt/user/Backups/` Verify it's no longer in the `app_data_cache/appdata` folder: `root@Chonk:~# ls /mnt/app_data_cache/appdata/hi.txt ` `/bin/ls: cannot access '/mnt/app_data_cache/appdata/hi.txt': No such file or directory` See that a `Backups` folder was now made on the wrong cache pool (should be the `cache` pool): `root@Chonk:~# ls /mnt/app_data_cache/` `Backups/ appdata/ system/` The `hi.txt` is on the wrong cache pool in the right directory: `root@Chonk:~# ls /mnt/app_data_cache/Backups/` `hi.txt` The right file always shows up in the right `/mnt/user/Backups` folder: `root@Chonk:~# ls /mnt/user/Backups/hi.txt ` `/mnt/user/Backups/hi.txt` The file does not exist on the right pool (verifying): `root@Chonk:~# ls /mnt/cache/Backups/` `/bin/ls: cannot access '/mnt/cache/Backups/': No such file or directory` If you can follow that series of commands, I create a hi.txt file and place it in the appdata folder, which lives on one cache pool. I then move that file over to my SwapSSD folder, which lives on another cache pool. The mv command is not moving the file to the other cache pool. Instead, it remains in the `app_data_cache`. When mover runs, it does not move this file to the array, I suspect because the named pool is wrong. when mover runs, with logging, I see this: Aug 26 13:53:04 Chonk move: file: /mnt/app_data_cache/Backups/hi.txt Aug 26 13:53:04 Chonk move: move_object: /mnt/app_data_cache/Backups/hi.txt File exists Upping the logging level to 2: Aug 26 13:54:39 Chonk move: debug: move: real_path: /mnt/app_data_cache/Backups/hi.txt Aug 26 13:54:40 Chonk move: file: /mnt/app_data_cache/Backups/hi.txt Aug 26 13:54:40 Chonk move: debug: create_parent: exclude 1 real_path /mnt/app_data_cache/Backups Aug 26 13:54:40 Chonk move: move_object: /mnt/app_data_cache/Backups/hi.txt File exists Aug 26 13:54:40 Chonk move: debug: move: real_path: /mnt/app_data_cache/Backups Aug 26 13:54:40 Chonk move: debug: move: move_object: /mnt/app_data_cache/Backups: Directory not empty At this time, I have no way to get the file off of the `app_data_cache` unless I manually move it to the other disk, so that mover can then do its thing. Is this a bug?
-
"Communication with Unraid webgui timed out after 30 seconds" linking my Unraid License
SOLVED: Went to the IP of my server and it worked fine. I was using a proxy domain. Woops.
-
-
"Communication with Unraid webgui timed out after 30 seconds" linking my Unraid License
Heya, I have a Pro license and I went to link my main Unraid server with MyServers; installed plugin, logged in, and go to "Finish Registration" where I am presented with the Register Server dialog. I see the right server and the right email/user account. I click "Confirm" and then 30 seconds later I get the Communication error. Do ports need to be open to use this plugin?
ephservers
Members
-
Joined
-
Last visited