Arragon

This feature could make ZFS way more interesting for Unraid in the future: https://github.com/openzfs/zfs/pull/12225

All of a sudden my flash drive was not writeable any longer. Searching for that error revealed that this most likely because of bad sectors and Sandisk making their drives readonly in that case. So I want to switch to a new drive but of course I don't have a flash backup. Now I wonder if I can just copy the files in Windows to the new one or if I need additional steps.

Does Remote Access require you to have have Port 443 accessible via IPv4? I can't get it to work with IPv6 even thought that can be reached from the internet.

I can confirm that since I still had issues with 6.9.0/2.0.3 and my raidz1 didn't change.

I think we can omit createtxg as it's described as "The birthtime transaction group (TXG) of the object."

Now that is strange. I have docker.img in it's own dataset on a raidz1. My settings NAME PROPERTY VALUE SOURCE tank/Docker type filesystem - tank/Docker creation Sun Feb 21 15:50 2021 - tank/Docker used 106G - tank/Docker available 22.8T - tank/Docker referenced 11.4G

@steini84 I have run 2.0.4 in 6.9.1 on my test system without a problem so far and switched my main system (raidz1, 24 docker containers in btrfs img) to unstable. Running fine for the last 8 hours where 2.0.3 under 6.9.0 had the system lock up within minutes. Looking like the issue is fixed in either Unraid 6.9.1 or ZFS 2.0.4. A verification from someone else would be helpful though.

Which problem are you referring to?

I have setup a test system with zfs 2.0.4 on Unraid 6.9.1 zpool of only one SSD drive znapsend making snapshots hourly one dataset for Docker placed docker.img in that dataset have one docker running (Telegraf) So far I could not reproduce the error. But there are some key differences to my main system when I had the problem, it had raidz1 of 3 drives zfs 2.0.3 on Unraid 6.9.0 multiple docker running drives where classic spinning rust Anyone got an idea on how to reproduce the error? I wouldn't call it fixed in 2.0.4

touch /boot/config/plugins/unRAID6-ZFS/USE_UNSTABLE_BUILDS

Is it still touch /boot/config/plugins/unRAID6-ZFS/USE_UNSTABLE_BUILDS ? I want to reproduce the problems on a test machine but only have 1 drive (since the array wants at least 1) and therefore could only create a single-disk pool. I don't know if that would result in me not being able to reproduce the docker error.

Like I said, I didn't even get to that point as the system completely locked up before I could copy over the data. Starting with a fresh Docker is not an option for me. Also the help page mentions ZFS for /var/lib/docker (where we want to bind-mount to). Currently they recommend btrfs (which Unraid uses by default) or OverlayFS (successor to aufs). I guess that is why it's currently an img-File and not simply a folder. I just don't understand what 2.0.1+ changed to make the img-File not work any longer. There was also something strange I noticed on 2.0.3 - I tried to copy

I'm still new to docker, so maybe I did it wrong. Here is what I thought I could do: 1) Create new dataset like /mnt/tank/Docker/image for the content that was previously in docker.img 2) Start Docker with docker.img and make sure containers are stopped 3) Copy over content from /var/lib/docker to /mnt/tank/Docker/image 4) Stop Docker and change path to /mnt/tank/Docker/image 5) Start Docker again and it would bind mount /mnt/tank/Docker/image to /var/lib/docker Unfortunately the system completely locked up during step 3 and I had to reset. EDI

After updating to 6.9.0 all my user shares are gone. /mnt looks like this d--------- 1 root root 0 Jan 1 1970 user/ and I can't change permission on that # chmod 1777 /mnt/user chmod: changing permissions of '/mnt/user': No such file or directory

Still running into the same problem with Docker. How can I go back to 2.0.0?