Cleanup after re-installing apps on a different pool

[bacon]

@Mastakilla

I did try with the fuser command at first, but that didn’t even return any processes (besides the kernel) for my ssdmaster-pool/.ix-apps mountpoint that contains running applications. So I considered my fuser command “invalid” because of that

Things can be a bit tricky. fuser is correct in this case. There are no processes with open files in ssdmaster-pool/.ix-apps. If you do something like this:

cd /mnt/.ix-apps
fuser -mM /mnt/.ix-apps

This will show the shell process, because the shell process has the folder open as current working directory.

If you do fuser -mM /mnt/.ix-apps/docker you would get the docker process.

In general, fuser might not be that useful for you - it can only tell you if there are processes which currently have open files within a dataset. I don’t think it recursively goes across mountpoints, so you have to be sure to pick the correct mountpoint.

@Mastakilla

For my new app installations, I only used host paths and tmp folders, never ixVolumes.

Good! That also explains why you don’t have any app_mounts datasets. If none of your hostpaths use the old ix-applications folders then you’re all good.

In my installation I have removed the ix-applications datasets without any repercussions.

There was a section in the manual about ix-applications, but I can’t find it now. The most official comment I could find is this:

Deleting apps from UI is not deleting app data from .ix-apps dataset

Electric Eel no longer uses ix-applications for apps data storage, moving it instead to /mnt/.ix-apps. That’s where changes to apps are reflected in 24.10 Data from previous app installs retained in the legacy ix-applications can be used to migrate or recreate applications in 24.10, but I’d say that once you have everything back up and running you should be able to safely delete the unused ix-applications dataset.