Piwigo: container creating 'extra' gallery folder

LSIO Discussion Container Support
1

I installed Piwigo configuring the /gallery folder to be in a piwigo share (/mnt/user/piwigo/) that I created on a pool device. That pool device is the third among my device pools that I have configured. That directory is created properly and contains my uploads, sub-folders, and images.

The three device pools are named;

  1. cache_f80_card (a pool of four devices formatted zfs)
  2. cache_nvme (a pool of two devices formatted btrfs)
  3. intolerant (a pool of one device formatted btrfs)

When ‘fix common problems’ ran It informed me that “Share piwigo set to use pool intolerant, but files / folders exist on the cache_f80_card pool”

When I check, there is an empty ‘uploads’ folder under a piwigo folder. When I try to ‘rm -rf /mnt/cache_f80_card/piwigo’ I get the error:
rm: cannot remove ‘piwigo/’: Device or resource busy

After I stop the Piwigo container I am able to delete the directory. As soon as I bring Piwigo back up the empty directory is back in the first device pool (cache_f80_card ).

My suspicion is that the reason this directory is being created in what would be considered the ‘first’ “cache” type pool and could be an artifact left over from back when Unraid had a single cache?

I double checked the share setup and the xml for the container and there is no hint as to why this is occurring.

It isn’t the end of the world, but this shouldn’t be happening. Has anyone else seen this behavior?

2

TLDR > not a piwigo issue, it was a DOH moment that was unraid ZFS related.

After some digging I realized that the reason for this problem was:

When I initially created the piwigo share the default cache was cache_f80_card, immediately after creating the share I changed the cache to the intolerant pool.
My mistake was in thinking that I only needed to delete the empty folder to clean up my mistake.
Because the initial pool was a zfs formatted pool it created a dataset and mounted the directory.
The fix was to run
# mountpoint piwigo
piwigo is a mountpoint
This indicated it was mounted. Then I ran
# zfs list
cache_f80_card/piwigo /mnt/cache_f80_card/piwigo
So to wrap up, I unmounted then destroyed with these two commands;
# zfs unmount /mnt/cache_f80_card/piwigo
# zfs destroy cache_f80_card/piwigo

Notice the paths are a bit different for the last two commands. The first is the mountpoint of the directory in question and the latter is the name of the dataset.