So as I said in an older thread, I converted my cache pool (single M2) to ZFS.

Everything works fine (had some minor issues but ok).

Cache usage show normal, about what it was before going ZFS.

 

But I did a "zfs list" and then verified with ZFS Master plugin, in my pool I see my normal few folders (which are not datasets AFAIK), BUT also see a few hundreds (!!!) of "legacy" datasets with names like "03747e08c1b7e6ab35ac74dc6c1538c83b1916185c5e4311e5899ec3d6911397"!

They also seem to be... snapshots?
(I never made snapshots myself)

 

What do I do, how do I clean those?

They don't show in normal folder listing.

 

 

That will happen if you use a docker folder with zfs, it's a zfs issue, you can use an xfs or btrfs image on zfs to avoid that.

14 minutes ago, JorgeB said:

That will happen if you use a docker folder with zfs, it's a zfs issue, you can use an xfs or btrfs image on zfs to avoid that.

 

I do use a docker image.

Is this an issue? Or just cosmetic?

 

46 minutes ago, NLS said:

I do use a docker image.

You mean folder? If yes it's mostly cosmetic, though I believe some users reported some performance issues if you start having hundreds of them.

 

 

5 minutes ago, JorgeB said:

You mean folder? If yes it's mostly cosmetic, though I believe some users reported some performance issues if you start having hundreds of them.

 

 

Yes I mean folder, sorry.

I have hundreds (maybe 250?) but I haven't noticed performance differences.

I do think ZFS might be overkill for this though.
Maybe I should revert to btrfs, although not very easy with all the VMs and containers.

 

On 7/5/2023 at 7:45 AM, JorgeB said:

That will happen if you use a docker folder with zfs, it's a zfs issue, you can use an xfs or btrfs image on zfs to avoid that.

I know this thread is a year old, but I done something similar. I moved everything to portainer, formatted my cache to zfs and have several of these legacy files now on my system folder with snapshots I never created. 

My question is can those files be deleted? if not do I have to go back to docker.img? or can as you suggested can I just copy my folders back to the array and format to xfs with in zfs? If this is a route I can take, how would I format xfs in zfs?

1 hour ago, gyrene2083 said:

My question is can those files be deleted? if not do I have to go back to docker.img? or can as you suggested can I just copy my folders back to the array and format to xfs with in zfs? If this is a route I can take, how would I format xfs in zfs?

 

I don't recommend using a docker directory with zfs on v6.12.x, you can go back to an image or re-format the pool xfs or btrfs, with v7.0.0-beta3 or newer, it should be OK to use a directory with zfs.

7 minutes ago, JorgeB said:

 

I don't recommend using a docker directory with zfs on v6.12.x, you can go back to an image or re-format the pool xfs or btrfs, with v7.0.0-beta3 or newer, it should be OK to use a directory with zfs.

So, I could either update to the beta  or move everything off the cache, reformat and copy everything back. I just want to make sure I understand before I do anything. I appreciate the help and suggestions you may have. 

1 minute ago, gyrene2083 said:

So, I could either update to the beta

es, but only when beta.3 or newer is out.

 

1 minute ago, gyrene2083 said:

or move everything off the cache, reformat and copy everything back

Like mentioned you can also go back to a docker image, that can be used with zfs.

16 minutes ago, JorgeB said:

es, but only when beta.3 or newer is out.

 

Like mentioned you can also go back to a docker image, that can be used with zfs.

Thank you for responding and your patience. I just worked so hard on learning how to use compose, and I learned some so it wasn't a failure and there is no easy way to go back to the compose image other than inputting everything manually correct?

Also, real quick. Going back to the docker.img, then can I delete those .legacy files from the system folder?

10 hours ago, gyrene2083 said:

way to go back to the compose image other than inputting everything manually correct?

Not sure, never used it.

 

9 hours ago, gyrene2083 said:

then can I delete those .legacy files from the system folder?

Yes.

@JorgeB

 

I am having same issue, 566 datasets(!!!) All marked as legacy on my zfs cache drive, how do inget rid of them or fix it?  Just so you are aware, I started my unraid journey with 7.0.1 so this is very fresh system

 

Looks like all of them were created by the docker, not sure why and how? What is the best approach to remove them and to stop them from being created? Should I just remove all data from this cache and format it as another file system if there is an issue with zfs?

Edited May 18, 20251 yr by Joloxx9

1 hour ago, Joloxx9 said:

am having same issue, 566 datasets(!!!) All marked as legacy on my zfs cache drive, how do inget rid of them or fix it?  Just so you are aware, I started my unraid journey with 7.0.1 so this is very fresh system

Upgrade to 7.1.2, that release can automatically delete all the legacy datasets when you delete the current docker folder, then recreate using the ovelar2 driver:

https://docs.unraid.net/unraid-os/release-notes/7.0.0/#add-support-for-overlay2-storage-driver

I have updated two days ago. What should I do now? Recreate apps in docker?

 

Sorry not sure how to use that overlay2 driver...

Edited May 18, 20251 yr by Joloxx9

7 minutes ago, Joloxx9 said:

Sorry not sure how to use that overlay2 driver...

See the link above, but basically, you just stop docker, check the box to delete the folder, then change the driver to oeveraly2 and recreate, finally yo need to restore the containers from previous apps.

 

 

 

 

5 minutes ago, JorgeB said:

See the link above, but basically, you just stop docker, check the box to delete the folder, then change the driver to oeveraly2 and recreate, finally yo need to restore the containers from previous apps.

 

 

 

 

Okay got it now, so I guess stuff like /appdata etc won't be affected? I just cannot see  "check the box to delete the folder" where is that thing?

Edited May 18, 20251 yr by Joloxx9

30 minutes ago, Joloxx9 said:

so I guess stuff like /appdata etc won't be affected?

Correct:

 

31 minutes ago, Joloxx9 said:

I just cannot see  "check the box to delete the folder" where is that thing?

Didn't have that field, however all dockers vanished etc so should be ok now, recreated all of them. Thanks for help. Myabe because array was offline?

Edited May 18, 20251 yr by Joloxx9

27 minutes ago, Joloxx9 said:

Myabe because array was offline?

Yep, it needs to be online, just stop the docker service.

1 hour ago, JorgeB said:

Yep, it needs to be online, just stop the docker service.

So I have to do it now? 

Should I just remove all files created before 18th of May?

 

Edited May 18, 20251 yr by Joloxx9

Do you still have the legacy datasets?

On 5/19/2025 at 8:57 AM, JorgeB said:

Do you still have the legacy datasets?

I wiped the folder, then manually erased all legacy databases and recreated docker, so far so good, no issues, thank you for your help :)

Edited May 21, 20251 yr by Joloxx9