Solved NFS mount not working.

[Mastadamus]

I have a NFS drive from my NAS mounted via this command in the /etc/fstab

(myserverIP):/mnt/array1/share /backups_nfs nfs rw,hard,tcp,rsize=8192,wsize=8192,timeo=14,x-systemd.automount 0 0

Here is the output of cat /proc/mount showing its been mounted

systemd-1 /backups_nfs autofs rw,relatime,fd=57,pgrp=1,timeout=0,minproto=5,maxproto= 5,direct,pipe_ino=16222 0 0

I'm getting an error everytime I try to select "nfs" as the backup location in the cloudron backup gui. It says "mountpoint must be an nfs filesystem" It works fine if i put that same path in of "/backups_nfs" as local filesystem. It will even write the backups to the share that way but it won't delete any.
Im at loss. Why is this showing as "autofs" and not NFS in cat /proc/mounts? Why won't cloudron delete old backups and why can't this mount as NFS.

Any guidance would be sorely appreciated.

[Mastadamus]

Mar 17 21:35:57 box:settings initCache: pre-load settings
Mar 17 21:35:57 box:taskworker Starting task 429. Logs are at /home/yellowtent/platformdata/logs/tasks/429.log
Mar 17 21:35:57 box:tasks 429: {"percent":2,"error":null}
Mar 17 21:35:57 box:tasks 429: {"percent":10,"message":"Cleaning box backups"}
Mar 17 21:35:57 box:backups applyBackupRetentionPolicy: 2021-03-16-040001-155/box_2021-03-16-040217-198_v6.2.4 box keepWithinSecs
Mar 17 21:35:57 box:backups cleanupBoxBackups: done
Mar 17 21:35:57 box:tasks 429: {"percent":40,"message":"Cleaning app backups"}
Mar 17 21:35:57 box:backups applyBackupRetentionPolicy: 2021-03-16-040001-155/app_ff0e491c-e723-4eb7-9309-e0caa67fb1d0_2021-03-16-040215-598_v1.6.1 app reference
Mar 17 21:35:57 box:backups applyBackupRetentionPolicy: 2021-03-16-040001-155/app_95032b2c-8726-4dce-9a65-a58885466d63_2021-03-16-040213-584_v1.5.0 app reference
Mar 17 21:35:57 box:backups applyBackupRetentionPolicy: 2021-03-16-040001-155/app_c370737a-1983-44a9-bbb4-889bbf933a49_2021-03-16-040214-427_v1.1.0-1 app reference
Mar 17 21:35:57 box:backups applyBackupRetentionPolicy: 2021-03-16-040001-155/app_8f9ee89f-bd3f-4628-8bc6-aabe2c0c5212_2021-03-16-040209-879_v2.14.1 app reference
Mar 17 21:35:57 box:backups applyBackupRetentionPolicy: 2021-03-16-040001-155/app_66b96d45-be9f-4b06-8f60-19b2b70e6f15_2021-03-16-040033-835_v1.2.1 app reference
Mar 17 21:35:57 box:backups applyBackupRetentionPolicy: 2021-03-16-040001-155/app_11c796fb-5871-4af9-96af-01572858a76b_2021-03-16-040030-731_v2.10.0 app reference
Mar 17 21:35:57 box:backups cleanupAppBackups: done
Mar 17 21:35:57 box:tasks 429: {"percent":70,"message":"Cleaning missing backups"}
Mar 17 21:35:57 box:tasks 429: {"percent":90,"message":"Cleaning snapshots"}
Mar 17 21:35:57 box:backups cleanupSnapshots: done
Mar 17 21:35:57 box:taskworker Task took 0.202 seconds
Mar 17 21:35:57 box:tasks setCompleted - 429: {"result":{"removedBoxBackupIds":[],"removedAppBackupIds":[],"missingBackupIds":[]},"error":null}
Mar 17 21:35:57 box:tasks 429: {"percent":100,"result":{"removedBoxBackupIds":[],"removedAppBackupIds":[],"missingBackupIds":[]},"error":null}

[robi]

It looks like your mount point is actually /mnt/array1/share/backups_nfs and not what you have in your screenie

[Mastadamus]

@robi Unfortunately, I tried it that way as well, i get same error message. The mount point theoretically, is just the folder i've mounted the share to. the first half of that /mnt/array1/share is my shared folder.. the actual mount is just /backups_nfs. I tried both though just to make certain and i get same error.

[nebulon]

@mastadamus this is actually a bug in the code. The mountpoint checker is based on /proc/mounts which in your case as you thankfully pasted, does not contain nfs as the type but some autofs not sure why we lost that information here.

For reference, the code is at https://git.cloudron.io/cloudron/box/-/blob/master/src/storage/filesystem.js#L291

@Mastadamus if you like, you could enable remote SSH support temporarily for us and send a mail to support@cloudron.io with your dashboard domain, then I could check how we can fix the filesystem type detection.

[robi]

@mastadamus there still seems to be an issue with that path because of the space after the 'share'.

@nebulon good catch on the mount type too

[Mastadamus]

@nebulon From my reading, if you do the system.automount option in the fstab it makes it autofs. This may be wrong, but I read that in multiple locations.

[Mastadamus]

@nebulon If I enable remote SSH, does it set a specific password for you all? how does that feature work? I'd have to open up my network firewall to ssh port as well correct?

[robi]

@mastadamus it's just a set of ssh keys for support. No passwords.

And yes, they would need a way to remotely connect either directly or via port forward.

[girish]

@mastadamus my understanding is that autofs is meant for mounting on demand. I guess we have two options here: Cloudron can add a autofs provider and look specifically for "autofs" type. Alternately, you can just mount it as NFS in the /etc/fstab . I think if you do the latter, it will work.

Essentially, change your current autofs line to be instead like below (i.e remove x-systemd.automount) . That flag was added in the docs when you have server that requires domain lookup, iirc :

(myserverIP):/mnt/array1/share /backups_nfs nfs rw,hard,tcp,rsize=8192,wsize=8192,timeo=14 0 0

After that, remount it and mount -a output will show nfs instead.

[Mastadamus]

@girish I did as you stated except I started completely over and created a new mount point named bu_nfs and then added the fstab entry. in proc/mounts i get the following now.

(myIP):/mnt/array1/share /bu_nfs nfs4 rw,relatime,vers=4.0,rsize=8192,wsi

yet when I put in /bu_nfs or /mnt/array1/share/bu_nfs inside cloudron gui, I get the same error message that it must be an NFS file system. Yet i can mount it as a local file system fine. It is showing nfs4 in proc/mounts though

[girish]

@mastadamus said in NFS mount not working.:

(myIP):/mnt/array1/share /bu_nfs nfs4 rw,relatime,vers=4.0,rsize=8192,wsi

Maybe because of the nfs4 above. Can you make it nfs?

[Mastadamus]

@girish What is the command to force it nsf instead of nfs4?

something like this?

myIP:/mnt/array1/share /bu_nfs nfs nfsvers=3 rw,hard,tcp,rsize=8192,wsize=8192,timeo=14 0 0

i think i need to specify which version..

[girish]

@mastadamus I meant like this (note that vers=4.0 i guess already means nfs4)

(myIP):/mnt/array1/share /bu_nfs nfs rw,relatime,vers=4.0,rsize=8192,wsi

[Mastadamus]

@girish Yes that line was the output of my proc/mounts. my fstab command was exactly as you wrote. Its automatically selecting nfs4. I think to force it to select an older version of NFS like ver 3 or 2 i have to manually input a nfsvers= command or vers= command

[Mastadamus]

@girish What version should I try to mount it as? Im guessing try 3?

[girish]

@mastadamus I think we want nfs4. Note that all we are trying to do here is to get the output of cat /proc/mounts to show nfs instead of autofs and nfs4.

[Mastadamus]

@girish ah im following you now. I have absolutely no idea how to make proc/mounts do that lol.

[girish]

@mastadamus what is the /proc/mounts output as it stands right now?

[Mastadamus]

@girish

This is the output of the proc/mounts

192.x.x.x:/mnt/array1/share /bu_nfs nfs4 rw,relatime,vers=4.0,rsize=8192,wsi ze=8192,namlen=255,hard,proto=tcp,timeo=14,retrans=2,sec=sys,clientaddr=192.x. x.x,local_lock=none,addr=192.x.x.x 0 0 (note i replaced my IP's with 192.x.x.x. not that it really matters lol)

[Mastadamus]

@mastadamus this is ubuntu 20.04lts

[nebulon]

@mastadamus we have to check if this nfs4 tag is the default now on ubuntu 20.04 and if not, would be interesting to see why your system behaves differently.

[Mastadamus]

@nebulon Cool just let me know. its not a big deal as of now, I have it mounted "local" in the cloudron gui and its still writing to the NFS mount it just can't delete for some reason.

[girish]

I have added nfs4 check for the next release. Searching around, I do see nfs4 in the output.

[Mastadamus]

@girish thank you, you may want to add autofs as well to the input the input check or alter the command listed in the documentation to reflect the guidance given in this thread to delete the system.automount portion

[girish]

@mastadamus yes https://git.cloudron.io/cloudron/box/-/commit/f3d9b8194264469152bc38d24d7080c611784b33