I'm having issues getting rid of a weird phantom error I'm receiving. It hasn't caused real problems lately in attempts at configuring things in OMV, so I put it off to solve later. Unfortunately later has come, as I'm trying to modify the folder location for Docker plugin, and hitting this issue again. Long story short on the background, I think there is some leftover buggy settings somewhere referring to old configurations I used at one point. I had a wealth of folders and I was mounting them all via NFS, then I changed to SMB, and then I reduced the amount of folders and restructured them to mostly be under one top level folder. The main problem folder now, is the Downloads folder referenced in the issue.
Error Message being posted on attempt to save Docker alternate root path update:
Error #0: exception 'OMV\ExecException' with message 'Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mkdir --parents --mode=0700 '/export/downloads' 2>&1' with exit code '1': mkdir: cannot create directory '/export/downloads': File exists' in /usr/share/php/openmediavault/system/process.inc:175 Stack trace: #0 /usr/share/php/openmediavault/system/mountpoint.inc(98): OMV\System\Process->execute() #1 /usr/share/openmediavault/engined/module/fstab.inc(84): OMV\System\MountPoint->create() #2 /usr/share/openmediavault/engined/rpc/config.inc(189): OMVModuleFsTab->startService() #3 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array) #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array) #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(150): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array) #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(528): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusHc...', '/tmp/bgoutput4t...') #7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(151): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure)) #8 /usr/share/openmediavault/engined/rpc/config.inc(208): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array) #9 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array) #10 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array) #11 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array) #12 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1) #13 {main}
Outputting the below shared folder and Shares from the associated services, so nobody tells me to just remove that share. I have and double checked them all to be sure. Still getting the message.
Current Shared Folders:
AFP Shares:
NFS Shares:
SMB Shares:
Dig a little deeper into the filesystem itself instead and we find these details - where even as root (sudo or sudo su), I can't delete or remove the export - get the message about resource busy
username @ atlantis/usr/share/php/openmediavault/system: ls /export/
ls: cannot access /export/downloads: No such file or directory
total 20K
drwxr-xr-x 8 root root 4.0K Dec 4 13:51 ./
drwxr-xr-x 25 root root 4.0K Apr 5 11:34 ../
drwxrwxr-x 2 storage users 6 Apr 19 11:05 dockerdata/
d????????? ? ? ? ? ? downloads/
drwx--x--x 8 storage users 131 Jan 19 23:16 home/
drwxrwsr-x 18 storage users 4.0K Mar 26 12:27 logs/
drwxrwsr-x 7 storage users 4.0K Mar 26 12:27 media/
drwxrwsr-x 4 storage users 4.0K Apr 10 23:00 temp/
Finally tried to check out /etc/fstab:
username @ atlantis/usr/share/php/openmediavault/system: cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdg1 during installation
UUID=dfad2da9-6ec9-4564-bde4-c1d015a85f59 / ext4 errors=remount-ro 0 1
# swap was on /dev/sdg5 during installation
UUID=94e5bb2a-914d-423b-95dd-3e14aa9240d0 none swap sw 0 0
tmpfs /tmp tmpfs defaults 0 0
# >>> [openmediavault]
UUID=97974d61-46e4-43fa-a535-54a31b4faec2 /media/97974d61-46e4-43fa-a535-54a31b4faec2 xfs defaults,nofail,noexec,usrquota,grpquota,inode64 0 2
UUID=53cc01be-f2be-4343-8cd9-80bf397f3647 /media/53cc01be-f2be-4343-8cd9-80bf397f3647 xfs defaults,nofail,noexec,usrquota,grpquota,inode64 0 2
UUID=812e34ce-571f-47ac-8943-27e1b5498f0c /media/812e34ce-571f-47ac-8943-27e1b5498f0c xfs defaults,nofail,noexec,usrquota,grpquota,inode64 0 2
UUID=b0bd1fd0-db04-4823-b3f8-f24fa445ac67 /media/b0bd1fd0-db04-4823-b3f8-f24fa445ac67 xfs defaults,nofail,noexec,usrquota,grpquota,inode64 0 2
/media/97974d61-46e4-43fa-a535-54a31b4faec2:/media/53cc01be-f2be-4343-8cd9-80bf397f3647:/media/812e34ce-571f-47ac-8943-27e1b5498f0c /media/04846b71-a903-47fd-add3-0019e9e1997a fuse.mergerfs direct_io,defaults,allow_other,category.create=epmfs,minfreespace=15G 0 0
/media/04846b71-a903-47fd-add3-0019e9e1997a/downloads /export/downloads none bind 0 0
/media/04846b71-a903-47fd-add3-0019e9e1997a/dockerdata /export/dockerdata none bind 0 0
/media/04846b71-a903-47fd-add3-0019e9e1997a/home /export/home none bind 0 0
/media/04846b71-a903-47fd-add3-0019e9e1997a/logs /export/logs none bind 0 0
/media/04846b71-a903-47fd-add3-0019e9e1997a/media /export/media none bind 0 0
/media/04846b71-a903-47fd-add3-0019e9e1997a/temp /export/temp none bind 0 0
/media/97974d61-46e4-43fa-a535-54a31b4faec2/docker /var/lib/docker/openmediavault none bind,defaults 0 0
# <<< [openmediavault]
Any help in outlining what could be wrong here and/or how I can clean this leftover lingering phantom mount? Should I be able to just pull out that fstab entry and be good? Or is there somewhere else I should be looking for the traces of this? Some other inner workings of OMV perhaps that stores the information that generates the fstab?