Can't mount MooseFS on Proxmox 8.1 properly. about moosefs

[PC-Admin]

I found the solution I was looking for!

There's an option with pve to prevent Proxmox fiddling with storage if a certain mountpoint isn't actually mounted:

root@jigglypuff:~# pvesm set Proxmox_Backups --is_mountpoint /mnt/Proxmox_Backups

Hopefully this is helpful to someone out there. :)

[PC-Admin]

This seems even crazier, despite commenting out the fstab entry completely it still seems to be badly mounting this after a reboot:

root@eevee:~# sudo fuser -vm /mnt/Proxmox_Backups/
                     USER        PID ACCESS COMMAND
/mnt/Proxmox_Backups:
                     root     kernel mount /
                     root          1 .rce. systemd
                     root          2 .rc.. kthreadd
                     root          3 .rc.. rcu_gp
                     root          4 .rc.. rcu_par_gp
                     root          5 .rc.. slub_flushwq
                     root          6 .rc.. netns
                     root          7 .rc.. kworker/0:0-events
                     root          8 .rc.. kworker/0:0H-events_highpri
                     root          9 .rc.. kworker/0:1-events
                     root         10 .rc.. kworker/u32:0-dm-thin
                     root         11 .rc.. mm_percpu_wq
                     root         12 .rc.. rcu_tasks_kthread
                     root         13 .rc.. rcu_tasks_rude_kthread
                     root         14 .rc.. rcu_tasks_trace_kthread
                     root         15 .rc.. ksoftirqd/0
                     root         16 .rc.. rcu_preempt
                     root         17 .rc.. migration/0
                     root         18 .rc.. idle_inject/0

That is very strange. After removing moosefs-client entirely it still seems like it's badly mounting it. (That doesn't even seem possible!)

root@eevee:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
udev                   32G     0   32G   0% /dev
tmpfs                 6.3G  1.3M  6.3G   1% /run
/dev/mapper/pve-root   24G  2.7G   21G  12% /
tmpfs                  32G   48M   32G   1% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
efivarfs              128K   11K  113K   9% /sys/firmware/efi/efivars
/dev/nvme1n1          1.8T  165G  1.6T  10% /mnt/Crucial_SSD
/dev/sda2             511M   12M  500M   3% /boot/efi
/dev/fuse             128M   72K  128M   1% /etc/pve
tmpfs                 6.3G     0  6.3G   0% /run/user/1000
root@eevee:~# ls /mnt/Proxmox_Backups/
dump  images  template
root@eevee:~# sudo fuser -vm /mnt/Proxmox_Backups/
                     USER        PID ACCESS COMMAND
/mnt/Proxmox_Backups:
                     root     kernel mount /
                     root          1 .rce. systemd
                     root          2 .rc.. kthreadd
                     root          3 .rc.. rcu_gp
                     root          4 .rc.. rcu_par_gp
                     root          5 .rc.. slub_flushwq
                     root          6 .rc.. netns
                     root          7 .rc.. kworker/0:0-events
                     root          8 .rc.. kworker/0:0H-events_highpri
                     root          9 .rc.. kworker/0:1-cgroup_destroy
...

[xandrus]

Hi!

What you get when you execute this command:

mfsmount -o allow_other,mfsmaster=mfsmaster.perthchat.org,mfsdelayedinit,_netdev,noexec,rw,mfspassword=REDACTED,mfssubfolder=/Proxmox_Backups /mnt/Proxmox_Backups

I suspect that mfsmount is not mouting because destination mount point is not empty(manged by Proxmox).
So please add nonempty mount option to fstab and execute mount -a command.

mfsmount /mnt/Proxmox_Backups fuse allow_other,mfsmaster=mfsmaster.perthchat.org,mfsdelayedinit,_netdev,noexec,rw,mfspassword=REDACTED,mfssubfolder=/Proxmox_Backups,nonempty  0 0

Please also check system log(journalctl -xe) in case of any error.

[PC-Admin]

Hi @xandrus

Thank you for the reply. Yes it seems like this is more of an issue with Proxmox then MooseFS.

I attempted to have Proxmox manage a subdirectory inside the mount point, but even then it seems to be re-creating that subdirectory and other directories inside it automatically when it has not yet been mounted.

pcadmin@jigglypuff:~$ ls /mnt/Proxmox_Backups/PC-Cluster/
ls: cannot access '/mnt/Proxmox_Backups/PC-Cluster/': No such file or directory
pcadmin@jigglypuff:~$ ls /mnt/Proxmox_Backups/PC-Cluster/
ls: cannot access '/mnt/Proxmox_Backups/PC-Cluster/': No such file or directory
pcadmin@jigglypuff:~$ ls /mnt/Proxmox_Backups/PC-Cluster/
dump  images  private  template

Attempting to mount another mount point that is not managed by Proxmox works fine. I am closing this issue now and will consult the Proxmox community for a solution.