No access to files from shares. about greyhole HOT 11 CLOSED

Hi.

This is most probably a permission problem with your storage pool drives.

See here for details : https://github.com/gboudreau/Greyhole/wiki/Permissions-Data-Drives

from greyhole.

I went through all the tips from the link.

Here you can see that the permissions are fine 775 and the file permission 777, but I get the same results even here.

from greyhole.

Did you try to login on your shell with the same user you use to connect to your share, to verify that this user can read the symlink, and the target?

from greyhole.

It's just the one user?

from greyhole.

Create a testfile inside the comicbooks/test/ folder, on your share, wait for Greyhole to process it and the problem to occur, then :

sudo su shroom
cd /mnt/drives/4TB001/landingzone/comicbooks/test
md5sum testfile
cd /mnt/drives/4TB002
cd gh
cd comicbooks
cd test
md5sum testfile

If you still can't figure out the problem, restart the Greyhole daemon, and try this: https://github.com/gboudreau/Greyhole/wiki/GetHelp#gather-system-information
And post the resulting URL in a new comment.

from greyhole.

http://ix.io/4fmJ

Thanks for taking time to look at this, it is appreciated.

I normally feel I can futz my way through problems and get things working, but am at a loss. So again, thanks.

from greyhole.

Somewhere in your Samba logs:

[2022/11/08 09:30:52] update-apparmor-samba-profile
  WARNING: "wide links" enabled. You might need to modify the smbd apparmor profile manually.

Maybe you have AppArmor configured to protect Samba, which prevents wide links in smb.conf from working?

from greyhole.

I don't know much about AppArmor, but if you can't figure out how to force it to allow Samba to access your storage pool drives, maybe this workaround would work : https://unix.stackexchange.com/a/493092/16277
Juste create a fake share that uses path = /mnt/drives, restart smbd, and I would guess AppArmor would then allow Samba to access the storage pool drives that will be under /mnt/drives

from greyhole.

Just an update:

Tried the above workaround and it provides a new share directly to the drives in the pool and from there I can access the files. However if I attempt to access the intended share with the symlinks it still gives the same error.

I went so far as to remove apparmor altogether but still came across the same issues, and pulled a new log and the same apparmor error was listed. I then did a fresh install of Ubuntu and before installing greyhole removed apparmor, but still have the same issue with the same apparmor reference in the logs.

Continuing to look at apparmor...

But guess I am also confused as I can't be the only one running Ubuntu 20.04...

from greyhole.

So may not have been apparmor after all.

Based on a bunch of reading and trying different things, the suggestion here worked:

https://unix.stackexchange.com/questions/5120/how-do-you-make-samba-follow-symlink-outside-the-shared-path/137192#137192

Added:

follow symlinks = yes
wide links = yes

to the actual share instead of [global] and the files just showed up and I can delete them as well...

I am hoping this is resolved now. Thanks for your patience in my issue.

from greyhole.

Thanks for the follow-up ; I added a note about this in the wiki page about this error.

from greyhole.