Remote folder shared normally

[mdi]

Here it is:

Code: Select all

root@nas:/ # /usr/sbin/showmount --no-headers -e [seagate nas ip addr]
/DataVolume/public (everyone)


Thanks,
MDI

[Jocko]

Thank, I think to understand where is the issue... And it is not a path issue
The firmware does not manage a line with the word "everyone" and without information about r/w access.
Tomorrow I go to examine this point.

[Jocko]

Hi

Nope there is no issue with your showmount output and indeed there was a stupid bug on the local path if it is too short... (it was present since version 14.0 ! :twak )

So I sent you a patch file to check if now you can mount your seagate nfs share on the lacie nas.

To do it open a shell terminal and runs these commands:

Code: Select all

 plugout download 6961
tar -xf /tmp/fvdw-sl-18-2-fix-remote-nfs-shr-11aug2022.tgz -C /

No need to reboot the nas and try to mount it now. :whistle

[mdi]

Hi Jocko,
thanks a lot! Now I can mount it as NFS and it seems it works in write mode both in NFS and SMB, directly from the NWSP2.

From my windows laptop instead I still have problems due to permissions, but I can see the shares (both in NFS and SMB), but I need to play more in order to understand why I cannot write/delete/update files or why windows get frozen when I try to access the NFS share via SMB.

I'll feedback as soon as I have news.

Many thanks so far, your fix was really helpful!!!

Current issue is that windows complains that it needs the authorization from User Unix/root when trying to write to the smb share and the Seagate Nas is mounted in Samba as well into the NWSP2.

It's curious that it seems to mount the NFS with proper permissions, while not with SMB. The shares created in rw_fw/etc/smb_add.conf are the same, only the mountpoint differs.

Code: Select all

drwxrwxr-x   5 root mdi   4096 2000-06-22 05:37 192.168.0.xxx-nfs-public
drwxr-xr-x   2 root root     0 2000-06-22 05:37 192.168.0.xxx-smb-public


Above, the first line (nfs) seems correct, as I use "mdi" as a user. The second seems not correct.
Anyway from windows I cannot write in either.
With NFS it seems I can create file, but after creating the file it takes a lot of time to return the control to Windows.... so the file explorer takes ages to be responsive.

[Jocko]

Hi

By setting some advanced mount options, I succeeded to enlarge write permissions on the mount point of a remote samba share. Also now the user 'nobody' has write permissions which is the user account used by samba by changing the group on the mount point

Code: Select all

ls -ald /share/1100/192.168.1.99-smb-Perso
drwxrwxrwx  2 Jocko sys 0 2022-03-01 16:32 /share/1100/192.168.1.99-smb-Perso

(nobody belongs to the group sys and 'Jocko' was the used login to mount the remote share)

Other change, on nfs remote share, sys is the group of the mount point (still to avoid issue with samba)

Code: Select all

ls -ald /share/1100/192.168.1.99-nfs-fvdw
drwxrwxrwx  29 root sys 12288 2022-06-08 14:12 /share/1100/192.168.1.99-nfs-fvdw


I hope with these last changes you can get write permissions over a samba access on the remote share. About the samba remote share I assume you have created on the lacie nas an user account with the same login used to mount the remote share If it still does not work I am sorry but no more idea :dry

Same way to install the edited file

Code: Select all

 plugout download 6964
tar -xf /tmp/fvdw-sl-18-2-fix-owner-remote-shr-12aug2022.tgz -C /

Note: currently I can not made a real test (I am not at home to do it...)

[mdi]

Hi Jocko,
many thanks!

Unfortunately I'm not able to install the patch with your instructions:

Code: Select all

root@nas:/rw_fs #  plugout download 6964
login successful
Fail to download!
logout successful
root@nas:/rw_fs # tar -xf /tmp/fvdw-sl-18-2-fix-owner-remote-shr-12aug2022.tgz -
C /
tar: /tmp/fvdw-sl-18-2-fix-owner-remote-shr-12aug2022.tgz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now


It seems the attachment is no longer available.

Thanks,
MDI

[Jocko]

Hi

I am sorry... I forgot to remove the lock on the file that I set before posting my previous message ! :oops:

So now all should work :whistle

[mdi]

Hi Jocko,
first the good news. It works and I can access the Seagate NAS via Samba.

Now the bad news :snicker :

This is what I get when mounting the Seagate NAS via Samba and via NFS:

Code: Select all

drwxrwxr-x   2 root mdi   4096 2000-07-02 20:59 192.168.0.xyz-nfs-public
drwxrwxrwx   2 mdi  sys      0 2000-07-02 20:59 192.168.0.xyz-smb-public


You mentioned that the 'sys' user should be used for NFS shares, but it seems it is applied to the Samba one.

At the moment, I can access the Samba share, but the writing speed is extremely low.
So I tried accessing the NFS share (still via Samba on the NWSP2), but it takes ages to answer. I don't think it is working.
If I try, from Windows, to access directly the NFS share on the Seagate NAS, so without accessing it via the NWSP2, it works quite normally and fast. Though I cannot use it from my backup software (Macrium Reflect) as it seems it doesn't support NFS pathnames.... :sob

[Jocko]

Hi

About nfs is amazing. I checked the last changes and no one may set mdi as group :scratch and permissions are not correct.
On the mount point you should get "rwxrwxrwx" and "root sys". I suggest you to make a new attempt but before remounting, you should check if their mount points has been really deleted.

So remove the nfs remote share from the web-interface and delete the mount point if it is still here (be careful there are two locations)

Code: Select all

ls -al  /rw_fs/tmp/mnt/

and delete the folder if it is still present

Code: Select all

rmdir  /rw_fs/tmp/mnt/192.168.0.xyz-nfs-public

and the 2d mount point

Code: Select all

ls -al  /share/1000/

and delete the folder if it is still present

Code: Select all

rmdir  /share/1000/192.168.0.xyz-nfs-public

Then retry to mount the nfs remote share.

If you still get the same output, please to do

Code: Select all

chgrp sys /rw_fs/tmp/mnt/192.168.0.xyz-nfs-public

(to see what the output returns)

[mdi]

Hi Jocko,
I got the same result. The share was already properly removed from all places and when I remounted it I got the same as before:

Code: Select all

root@nas:/rw_fs/tmp/mnt/remote_share_mount_dir # ls -l
total 4
drwxrwxrwx  2 mdi  sys    0 2020-11-29 14:58 192.168.0.148-smb-data1
drwxrwxr-x  3 root mdi 4096 2000-07-05 20:52 192.168.0.159-nfs-public
drwxrwxrwx  2 mdi  sys    0 2000-07-05 20:52 192.168.0.159-smb-public
root@nas:/rw_fs/tmp/mnt/remote_share_mount_dir # chgrp sys 192.168.0.159-nfs-pub
lic
chgrp: changing group of `192.168.0.159-nfs-public': Operation not permitted
root@nas:/rw_fs/tmp/mnt/remote_share_mount_dir # whoami
root