[Samba] Eclipse (Java) locking issues after upgrade (3.6.23 -> 4.4.3)
jra at samba.org
Fri May 20 22:05:30 UTC 2016
On Fri, May 20, 2016 at 12:01:20PM -0400, Luc Lalonde wrote:
> by: java.io.IOException: An error occurred while locking file
> "Operation not supported". A common reason is that the file system or
> Runtime Environment does not support file locking for that location.
> Please choose a different location, or disable file locking by passing
> "-Dosgi.locking=none" as a VM argument.
> at org.eclipse.osgi.internal.location.Locker_JavaNio.lock(Locker_JavaNio.java:49)
> at org.eclipse.osgi.storagemanager.StorageManager.lock(StorageManager.java:388)
> at org.eclipse.osgi.storagemanager.StorageManager.open(StorageManager.java:701)
> at org.eclipse.osgi.storage.Storage.getChildStorageManager(Storage.java:1785)
> at org.eclipse.osgi.storage.Storage.getInfoInputStream(Storage.java:1802)
> at org.eclipse.osgi.storage.Storage.<init>(Storage.java:128)
> at org.eclipse.osgi.storage.Storage.createStorage(Storage.java:87)
> at org.eclipse.osgi.internal.framework.EquinoxContainer.<init>(EquinoxContainer.java:66)
> ... 10 more
> mac-mini:MacOS user$ mount
> /dev/disk0s2 on / (hfs, local, journaled)
> devfs on /dev (devfs, local, nobrowse)
> map -hosts on /net (autofs, nosuid, automounted, nobrowse)
> map auto_home on /home (autofs, automounted, nobrowse)
> map -fstab on /Network/Servers (autofs, automounted, nobrowse)
> //user at sambafileserver.foo.bar/user <http://email@example.com/p302568> on /home/user (smbfs, nodev, nosuid, automounted, nobrowse, mounted by user)
> The client is a Mac-Mini running OSX Yosemite with Java 8, update92.
> We have no problems with Windows 10 clients.
> Here are the pertinent configuration directives active on the Samba server:
> kernel oplocks = yes
> strict locking = No
> oplocks = yes
> level2 oplocks = yes
> deadtime = 15
> unix extensions = yes
> wide links = yes
> allow insecure wide links = yes
> What's strange is this was working fine with Samba v3.6.23. We
> don't have any problems with Windows clients.
Turn off "kernel oplocks = yes", you don't need this
if all access is via Samba.
Do you have a debug level 10 log from the server
showing access requests at the time of the failure ?
More information about the samba