January 12, 20251 yr Community Expert I followed spaceinvaders videos some time back to convert two disks (my cache and my nvme pool) to zfs, and then implemented his sanoid autobackup system which has been working flawlessly. One thing I have not liked after doing all that however is the file system view of the docker files - as i am using the docker folder method, not the docker image. All the lagacy stuff in the zfs master plugin (attached). I know this was an ortifact of doing all this work but my questiosn are this : 1 - will the unrad upgrade fix all this ? as I assume zfs is native now and the zfs aster plugin will not be used ? 2 - do I need to do anything with the plugin befoe upgrade ? 3 - should I convert my dockers back to image before upgrading ? 4 - will the unradi V7 upgrade hurt or change in anyway the setup wok for the sanoid autobackup scripts from spaceinvader ? Thanks in advance.
January 12, 20251 yr Community Expert 7 hours ago, vw-kombi said: will the unrad upgrade fix all this ? Yes, if you change to the ovcerlay2 driver and recreate the folder, but will need to manuall delete all the legacy datasets to remove them.
January 14, 20251 yr Author Community Expert Should I change back to a docker image then before hand ? Get this all clean on the current system before unraid 7 upgrade. I have a backup unraid system that I can 'play' with for all this. So I have 'broken' it to match - i.e change the three dockers to file system, and now that systm shows a load of legacy files. I still have no idea what they are. So If I convert back to the docker vdisk method instead, I still see all these legacy things. And I can just delete them ?
January 14, 20251 yr Community Expert 1 hour ago, vw-kombi said: Should I change back to a docker image then before hand ? Get this all clean on the current system before unraid 7 upgrade. That may be easier to clean up.
January 14, 20251 yr Author Community Expert I did that process on my backup unraid server. Now to plan for the real one - but there are so many of these legacy files, and one at a time is going to be a real pain on this system.
January 15, 20251 yr Author Community Expert I have about 475 of these legacy things around. A one by one is going to take a while........ I did notice on the backup system than when selecting dependencies, others were being deleted - so hopefully there are a load of those.......
January 15, 20251 yr Community Expert 12 hours ago, vw-kombi said: but there are so many of these legacy files, and one at a time is going to be a real pain on this system. If the docker folder was a dataset you can remove the complete dataset, post the output from zfs list It can be to a txt file
January 18, 20251 yr Author Community Expert Thanks for the help. Sorry for the delay, i have attached this text file. zfs-list.txt
January 18, 20251 yr Community Expert It wasn't a dataset, so they are on the root pool, meaning you would need to destroy them one by one, or maybe someone could make a script, another option is to backup and recreate the pool.
January 30, 20251 yr Author Community Expert Solution Just an update to this post as I have completed the process. I had 2 hours free early yesterday morning, and no user impact, so I saved the flash drive and updated to V7. All fine and took minutes. I then stopped docker, change back to a docker image and restarted. Re-installed al containers and all back up and running. Then I started the long process (about 1.5 hours) or deleting al the legacy files there. The process got faster as they got less and less. I now have a nice clean filesystem, and the docker size is sitting around 39% do i am in no ush to convert back to the docker directory method.
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.