December 5, 2014

Debian 4.0 and mounting to a Windows Storage Server 2012 R2 NFS Share

I am new to Linux, and need some help. We have a Linux server running Debian 4.0, that needs to connect to a share on a Windows 2012 Storage Server R2 NAS device.

I've configured the Windows share for NFS, and mounted the share on the Linux server successfully (we tried using cifs, but that doesn't work either...with more issues).
On the Linux server, the mounted directory is set for drwxrwxrwx, but when a user creates/saves a file, the permissions on the file are set as -rw-r--r--.

We are using the following command in /etc/fstab to mount the share:

:/Data /mnt/Windows nfs rw,_netdev

How do I configure this so that when the Linux user saves a file, the permissions are set to -rw-rw-rw- or -rwxrwxrwx?

Roide, what did you do that fixed the issue?...

Roide, what did you do that fixed the issue?

If you create a directory on a linux system and decide to change the permissions on it, use the -R options before the desired permissions.

#sudo chmod -R

The -R options will change all permissions of file and directories to the permission set on the parent directory.

Something interesting I just learned, you can use KDE's konquerer version 4.13.3 to view permissions of files and directories. Install konquerer from synaptic or apt. Open the browser and click home folder from the front page. A directory tree of your profile's directories is displayed. Click the view menu on the menu bar, go to "additional information", go to other, and select permissions. You will all permissions of the files and directories.

As for NFS, to allow access to a mounted share from a Linux server that uses NFS(ubuntu for example), the permissions of the user's group on the client must match the permissions of the group on the share of the server. Make sure that users and shares are all part of the same group with identical permissions.

Let me know if this is similar to what you did.

Like  (0 likes)

Getting umask properly set up resolved the issue.

Getting umask properly set up resolved the issue.

Like  (0 likes)
Click Here!