NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
csousa
Jan 17, 2015Aspirant
CIFS Mount From Raspian Linux - Permissions
My Setup Overview:
ReadyNas NV+ running latest RAIDiator 4.1.14 [1.00a043]
The ReadyNas security option is set to "Share" security as this is a home-based NAS.
Client: Raspberry Pi running Raspian (Linux) with cifs utilities installed and operational.
Symptoms:
- I can successfully mount and access the ReadyNas. I can also create new files. All new files created are write protected by default and I can't figure out why (i.e., by default I cannot modify any files I create ...I can create a zero byte file but can't open it for write access).
- I can remedy the issue (not solve it) by "resetting permissions on the share from FrontView on my ReadyNas.
- An "ls -l" directory listing shows that the files created belong to the Test user and nogroup which is controlled by the ReadyNas.
- The issue seems to be related to default permissions for non-owners not being picked up by linux.
I am using the following command:
sudo mount //192.168.1.196 /media/readynas/Test -t cifs -o username=Test,password=
Things I have checked
- I have a CIFS share called "Test" which is setup correctly (no issues from my MacBook OS/X)
- checked permissions on the mount point in Linux to ensure it is open (777)
Anyone have a similar setup. I basically want my ReadyNas CIFS shares "wide open" so that my Raspberry Pi can read/write freely to/from them.
ReadyNas NV+ running latest RAIDiator 4.1.14 [1.00a043]
The ReadyNas security option is set to "Share" security as this is a home-based NAS.
Client: Raspberry Pi running Raspian (Linux) with cifs utilities installed and operational.
Symptoms:
- I can successfully mount and access the ReadyNas. I can also create new files. All new files created are write protected by default and I can't figure out why (i.e., by default I cannot modify any files I create ...I can create a zero byte file but can't open it for write access).
- I can remedy the issue (not solve it) by "resetting permissions on the share from FrontView on my ReadyNas.
- An "ls -l" directory listing shows that the files created belong to the Test user and nogroup which is controlled by the ReadyNas.
- The issue seems to be related to default permissions for non-owners not being picked up by linux.
I am using the following command:
sudo mount //192.168.1.196 /media/readynas/Test -t cifs -o username=Test,password=
Things I have checked
- I have a CIFS share called "Test" which is setup correctly (no issues from my MacBook OS/X)
- checked permissions on the mount point in Linux to ensure it is open (777)
Anyone have a similar setup. I basically want my ReadyNas CIFS shares "wide open" so that my Raspberry Pi can read/write freely to/from them.
4 Replies
Replies have been turned off for this discussion
- Further to my original post, I think the issue is on the ReadyNas side of the equation but is specific to Linux mounted shares. A CIFS share mounted and used from Mac OSX is fine as well.
The odd behaviour from the Pi is that I can:
1) Copy files created on the Pi elsewehre to the ReadyNas.
2) Delete those files or files created by others.
3) Create an empty file.
But I cannot open a file for writing/overwrite on the NAS from the Pi.
The owner/group ID of the created files (when seen from the NAS) are correctly set to the Share Username and nogroup, however, the rwx permissions are not "wide open" as they should be. - mdgm-ntgrNETGEAR Employee RetiredShare mode is long EOL (End of Life) and we don't recommend using this any more.
Have a read of this article and see if it helps: http://readynas.sphardy.com/2010/09/how-to-migrate-to-user-security-mode_4917.html - Thanks for the tip. I'll flip over to authentication mode and see if my Linux mount operates normally.
- The recommended changes (moving away from Share security mode) worked perfectly. In fact I enabled the NFS protocol and the Raspian OS (Debian Linux) mounts and works with my NAS flawlessly. The legacy "Share" security, while allowing mounts, does not handle permissions properly.
Thanks for the tip.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!