DietPi-Drive_Manager | Add correct NFSv3 fstab entry handling

[mgherghi]

so after the most recent update i think nfsv3 is working but when i mount the share it gives me the following error:

mount.nfs: access denied by server while mounting 192.168.1.1:/

[mgherghi]

everything is setup properly on the server side, because i have another client setup using the same method

[MichaIng]

@mgherghi
Jep that is a known issue. Hmm we should have made this a bid clearer in changelog 🤔:
See: https://github.com/Fourdee/DietPi/issues/1898#issuecomment-406437446

So you manually need to add the path to the NFS export to the clients /etc/fstab entry. We will add full NFSv3 functionality to dietpi-drive_manager with v6.13. As it is a bid hacky to get this to work, we couldn't resolve it for v6.12 any more. It was already much luck inside to find the actual reason for general NFSv3 support last yesterday night due to changes on APT repo side (obviously), so forgive us the not yet fully completed solution 😉.

I leave this issue opened and rename it, so we use it for full NFSv3 implementation into dietpi-drive_manager

[mgherghi]

I apologize but how should i add the path in fstab ?

[MichaIng]

@mgherghi
That depends on the NFS server, where the location of the shared folder is found within file system.

On default DietPi NFS server setup it would be:

192.168.1.1:/mnt/dietpi_userdata instead of just 192.168.1.1:/

Which other client setup you have and how exactly did you add the NFS drive there?

[MichaIng]

PR to solve this is up: https://github.com/Fourdee/DietPi/pull/1994
Testing across some setups and distro versions makes sense to verify the error message, that indicates NFSv3, is matched correctly.

[MichaIng]

@Fourdee
Did you test on your machines? Can this be closed?

[Fourdee]

sh: 0: getcwd() failed: No such file or directory
Selecting previously unselected package netbase.
(Reading database ... 11685 files and directories currently installed.)
Preparing to unpack .../0-netbase_5.4_all.deb ...
Unpacking netbase (5.4) ...
Selecting previously unselected package libevent-2.0-5:arm64.
Preparing to unpack .../1-libevent-2.0-5_2.0.21-stable-3_arm64.deb ...
Unpacking libevent-2.0-5:arm64 (2.0.21-stable-3) ...
Selecting previously unselected package libnfsidmap2:arm64.
Preparing to unpack .../2-libnfsidmap2_0.25-5.1_arm64.deb ...
Unpacking libnfsidmap2:arm64 (0.25-5.1) ...
Selecting previously unselected package libtirpc1:arm64.
Preparing to unpack .../3-libtirpc1_0.2.5-1.2_arm64.deb ...
Unpacking libtirpc1:arm64 (0.2.5-1.2) ...
Selecting previously unselected package keyutils.
Preparing to unpack .../4-keyutils_1.5.9-9_arm64.deb ...
Unpacking keyutils (1.5.9-9) ...
Selecting previously unselected package rpcbind.
Preparing to unpack .../5-rpcbind_0.2.3-0.6_arm64.deb ...
Unpacking rpcbind (0.2.3-0.6) ...
Selecting previously unselected package nfs-common.
Preparing to unpack .../6-nfs-common_1%3a1.3.4-2.1_arm64.deb ...
Unpacking nfs-common (1:1.3.4-2.1) ...
Setting up libnfsidmap2:arm64 (0.25-5.1) ...
Setting up keyutils (1.5.9-9) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Setting up libtirpc1:arm64 (0.2.5-1.2) ...
Processing triggers for systemd (232-25+deb9u4) ...
Setting up libevent-2.0-5:arm64 (2.0.21-stable-3) ...
Setting up rpcbind (0.2.3-0.6) ...
Created symlink /etc/systemd/system/multi-user.target.wants/rpcbind.service → /lib/systemd/system/rpcbind.service.
Created symlink /etc/systemd/system/sockets.target.wants/rpcbind.socket → /lib/systemd/system/rpcbind.socket.
Setting up netbase (5.4) ...
Setting up nfs-common (1:1.3.4-2.1) ...

Creating config file /etc/idmapd.conf with new version
Adding system user `statd' (UID 106) ...
Adding new user `statd' (UID 106) with group `nogroup' ...
Not creating home directory `/var/lib/nfs'.
Created symlink /etc/systemd/system/multi-user.target.wants/nfs-client.target → /lib/systemd/system/nfs-client.target.
Created symlink /etc/systemd/system/remote-fs.target.wants/nfs-client.target → /lib/systemd/system/nfs-client.target.
nfs-utils.service is a disabled or a static unit, not starting it.
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for systemd (232-25+deb9u4) ...

[  OK  ] DietPi-Drive_Manager | G_AGI: nfs-common netbase
/DietPi/dietpi/dietpi-drive_manager: line 1876: .mount_out: No such file or directory
grep: .mount_out: No such file or directory

Stuck in loop, asking me for details

FP_WORK_DIR='/tmp/dietpi-drive_manager' Missing:

[  OK  ] DietPi-Drive_Manager | Detecting unmounted drives, please wait...
/DietPi/dietpi/dietpi-drive_manager: line 322: .dietpi-drive_manager_blkid_tmp: No such file or directory
/DietPi/dietpi/dietpi-drive_manager: line 116: .dietpi-drive_manager_blkid_tmp: No such file or directory
/DietPi/dietpi/dietpi-drive_manager: line 379: .dietpi-drive_manager_lsblk_tmp: No such file or directory
/DietPi/dietpi/dietpi-drive_manager: line 116: .dietpi-drive_manager_lsblk_tmp: No such file or directory
cp: cannot stat '.fstab': No such file or directory
rm: cannot remove '.fstab': No such file or directory

Strange, restored backup and re-run, its fine 😕 .

• Restore
• Reboot
• Failed again

root@DietPi:~# cat debug
DietPi-Backup | DELETED
DietPi-Obtain_network_details | DELETED
DietPi-Banner | DELETED
DietPi-Obtain_network_details | DELETED
DietPi-LED_Control | DELETED
DietPi-CPU_set | DELETED
DietPi-Obtain_network_details | DELETED
DietPi-Banner | DELETED
DietPi-Boot | DELETED
DietPi-Process_tool | DELETED
DietPi-Services | DELETED
DietPi-Banner | DELETED
DietPi-Run_ntpd | DELETED
DietPi-Update | DELETED /tmp/dietpi-update
DietPi-Obtain_network_details | DELETED
DietPi-Banner | DELETED
DietPi-Services | DELETED
DietPi-Drive_Manager | DELETED /tmp/dietpi-drive_manager
DietPi-Obtain_network_details | DELETED
DietPi-Banner | DELETED

Hmm,

[[ $FP_WORK_DIR && -d $FP_WORK_DIR && $G_PROGRAM_NAME pgrep not running? ]] && rm -R $FP_WORK_DIR

...

root@DietPi:~# pgrep -ci 'dietpi-drive'
2
root@DietPi:~# pgrep -ci 'dietpi-drive_manager'
0
root@DietPi:~# pgrep -ci 'dietpi-drive\_manager'
0
root@DietPi:~# pgrep -ci 'dietpi-moocow'
0


root@DietPi:~# ps aux | grep dietpi-drive_manager
root      2678  0.2  0.1   6772  4996 pts/0    S+   14:02   0:00 /bin/bash /DietPi/dietpi/dietpi-drive_manager
root      2885  0.0  0.1   6772  4104 pts/0    S+   14:02   0:00 /bin/bash /DietPi/dietpi/dietpi-drive_manager

Requires -f for _ support

root@DietPi:~# pgrep -cif 'dietpi-drive_manager'
3
root@DietPi:~# pgrep -cif 'dietpi-drive_managerx'
0

[Fourdee]

@MichaIng

Yes does work, minus the FP_WORK_DIR issue. Will mark this as closed 👍

[Fourdee]

REF: https://github.com/Fourdee/DietPi/issues/1997