因此，我做了大量的研究试图解决这个问题，但几个小时后，我却陷入了困境。
我知道这与权限有关，但我完全不知道如何修复它。我可以从 Windows 10 框和 Ubuntu 17.10 框读取我的 samba 服务器。samba 服务器在 Raspberry Pi 3 上运行，它运行最新版本的 Raspbian Lite（如果您不知道，它基本上是轻量级的 Debian Stretch）。我有一个测试硬盘（只是一个 USB 驱动器），在 上，/dev/sda1我的共享文件夹在 中/media/USBHDD/share。
因此，我将转储smb.conf我的媒体目录的文件和权限，希望你们中有人能帮助我理解这一点。
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
#======================= Global Settings =======================
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no
#### Networking ####
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes
security = user
#### Debugging/Accounting ####
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Cap the size of the individual log files (in KiB).
max log size = 1000
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
####### Authentication #######
# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
server role = standalone server
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam
obey pam restrictions = yes
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<[email protected]> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user
########## Domains ###########
#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set
#
# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U
# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u
# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g
############ Misc ############
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100
# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes
#======================= Share Definitions =======================
[homes]
comment = Home Directories
browseable = no
# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
read only = yes
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
create mask = 0700
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
directory mask = 0700
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes
valid users = %S
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700
[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin
[share]
comment = Pi shared folder
path = /media/USBHDD/share
browseable = yes
read only = no
create mask 0660
directory mask = 0771
valid users = backups MYUSERNAME root
force user = MYUSERNAME
ls -l我的输出/media/USBHDD/share是：
rwxr-xr-x 2 root root 16384 Dec 30 20:21 Documents
drwxr-xr-x 2 root root 16384 Dec 30 20:21 Miscellaneous
drwxr-xr-x 2 root root 16384 Dec 30 20:21 Pictures
此外，如果您ls -l需要share/：
drwxr-xr-x 6 root root 16384 Dec 30 20:21 share
感谢您阅读本文。我非常感谢能得到的所有帮助。
编辑：我忘了提到 /dev/sda1 是 NTFS 格式的驱动器，因为它正在被 Windows 机器访问。这使得 chown 和 chmod 无法工作。
答案1
从您的评论中：
我忘了说，驱动器
/media/USBHDD/shares已格式化为 NTFS，以便在 Windows 上可读。这使得无法使用chown和进行更改chmod，这两个解决方案我都试过了。
我猜你正在使用ntfs-3g。在这种情况下，你应该研究它的以下挂载选项：uid，gid，dmask，fmask。你应该做的第一件事是传递uid=MYUSERNAME给挂载驱动器的任何机制。这将使文件系统看起来好像其中的所有内容都属于MYUSERNAME。
如果你通过以下方式安装fstab，正确的方法应该类似于这个问题中的一个（但请阅读我的回答）。该路径/media/…表明驱动器可能由某种自动安装程序安装；如果是这样，那么您应该配置其选项。
我原来的回答中的一些部分（如下）适用于支持 UNIX 权限的文件系统。对于 NTFS，chown您应该在安装时传递正确的uid和。gid
原始答案：
您的共享及其下的对象归所有者所有，root并且只有所有者才具有写入权限。我在ls -l输出中谈论的是 UNIX 权限，这本身与 Samba 无关。
然后，Samba 强制任何有效用户（valid users = backups MYUSERNAME root；这些是 Samba 用户，不一定是 UNIX 用户）在 UNIX 权限上下文中为MYUSERNAME( force user = MYUSERNAME)。此用户没有写权限。
可能的解决方案：
让
MYUSERNAME拥有共享的一切：sudo chown -R MYUSERNAME: /media/USBHDD/share授予每个用户对共享中的所有内容的写权限：
sudo chmod -R +w /media/USBHDD/share以上内容的组合，可能缩小范围；或使用组访问的解决方案；现在您知道问题是什么了，因此问问自己，您想将什么资产的什么权限授予谁。
force user = root（如果可能的话），但这样做很愚蠢。
其中一些解决方案在不同的 Samba 配置下会更好地发挥create mask作用directory mask。研究并理解其含义。