Hi again everybody.
Ive gone further in my little samba share project, and ran into new problems i cant seem to find solutions to on google.
My mount “share” works great.
But i created 3 new subfolders in /share and mounted 3 new harddisks in the folders. i see them all fine from console and have full rights but they dont show when i access “share” from a windows client.
smb.conf
[global]
workgroup = WORKGROUP
server string = Samba
netbios name = Medie
security = user
map to guest = bad user
dns proxy = no
ntlm auth = true
log file = /var/log/samba/%m
log level = 1
[share]
path = /share/
read only = no
guest ok = yes
guest only = yes
~
is there a reason why you don’t combine the three disks and the space that you have available on / into a single volume using LVM. You could then mount it to /shareand share it using samba.
(to make the available space on / available, you need a seperate partition instead of extending your root partition into the free space, as per your previous post.
If one fails, it would be sad to loose whatever was stored one that one drive.
So either, cater for backups or don’t store anything that you can’t afford to loose on those drives.
Your right about that and ill look into that.
But the problem persists though.
I actually cant access any of the drives from samba at all. Now i just tryed to share a folder i called render1 where drive1 is mounted. I cant access that at all. I cant figure out what ive done wrong. Is it in the fstab or how come i get this problem. Im fairly new to fedora.
Ive never had this problem in debian, ubuntu or arch linux.
and that user is not intended to own anything or run any processes as I recall. It is usually a catch-all for when ownership of things go wrong.
I have never seen a listing of files/directories that showed user&group ownership by nobody (except possibly a misconfigured samba server using an ntfs file system.)
It was some guide i found for full guest access without any hassle.
Do you believe the problem is the ownership? Ill try to add a normal user and give that user ownership and see if i can mount the harddisks. I just cant find the logic to why i can access the folders on the samba just not the harddisk mounted folders?
Not having a Windows system at hand, I tested with smbclient and it seems to work in this way. Even a legal user creates nobody files on the share. No idea whether SELinux can block things on a mounted drive, if enabled.
If possible via direct view or ssh, you can stop the smb service on the server, and start smbd in foreground with:
smbd -d 2 --debug-stdout -F --no-process-group
Increase the debug level until you get an idea why it does not work. Or examine the smb logfiles.