Posts by mluna

    I found out that as "dev-disk-by-id-ata-WDC_WD2502ABYS-18B7A0_WD-WCAT1E266347-part1" didn't have execute permissions on Others, "share1" folder was unnaccessible through SMB, but as I said before, Why are the mountpoint permissions different from others?

    I have two shares with identical permissions / ACL.

    "share1" and "share2"

    drwxr-sr-x+ 2 mluna local-share 4.0K Jun 4 10:46 share1

    drwxr-sr-x+ 4 mluna local-share 4.0K May 30 21:04 share2

    Both have "guest allowed" set.

    I can't access "share1" as Windows 10 returns an error stating that "share1" is not accessible due to permissions, but I can access "share2" without problems.

    The only thing I found different was permissions on the mountpoints (which are different HDD's):

    drwxr-xr-x 8 root root 4.0K May 30 21:04 dev-disk-by-id-md-name-NAS-0

    drwxr-srw-+ 3 root local-share 4.0K Jun 4 10:46 dev-disk-by-id-ata-WDC_WD2502ABYS-18B7A0_WD-WCAT1E266347-part1

    "share1" is on "dev-disk-by-id-ata-WDC_WD2502ABYS-18B7A0_WD-WCAT1E266347-part1".

    Why does these mountpoints have different permissions if I created both filesystems the same way (through OMV web interface)?

    I've created the same share before on the same drive and it didn't have that problem before as it was acessible through the entire network without issues.