After I merged 4 older shares into 1 new one, almost whole of that map structure is on cache disk, folders only, no files.
Both old and new shares were array only.

Location: cache

Last modified: 7 days ago

Total occupied space: 0 B

in 8415 folders and 0 files

While the share has about 10,000 folders.

Is this normal? I've deleted the old shares, so I can't check if it was the same on the old and don't remember.

Is there a risk? Share warning says "Some or all files unprotected", I'm guessing that's a false positive. But I also dare not delete the folders manually from cache (is that safe?).

Last change on the file structure for that share on the cache disk is about a week ago, which is around the time I migrated, so it seems whatever put them there don't put them there anymore.

Attach Diagnostics ZIP to your NEXT post in this thread.

Did you remove the empty share folder from the pool device? Do you have a docker container or plugin creating a top level folder on the cache pool with an erroneous path saved somewhere?

1 hour ago, MowMdown said:

Did you remove the empty share folder from the pool device?

Not manually no, just removed the shares after moving the files between shares.
But it's the new shares structure that's on the cache disk.

1 hour ago, MowMdown said:

Do you have a docker container or plugin creating a top level folder on the cache pool with an erroneous path saved somewhere?

Oh, maybe. Didn't consider they can override. None have explicit access to disks, just shares, but perhaps a "bug" somewhere. I'll do some digging there.

By your post I understand it's not normal behavior. Thanks!

If a container writes to a share that is configured as "primary cache"

OR

/mnt/cache/sharename it will create a new folder on the cache pool.

posting diagnostics will give everyone a better idea what you have setup