[Samba] Eclipse (Java) locking issues after upgrade (3.6.23 -> 4.4.3)

Luc Lalonde Luc.Lalonde at polymtl.ca
Fri May 20 16:01:20 UTC 2016


Hello,

We seem to not be able to use Eclipse with a network drive since we 
upgraded our Samba server to version 4.4.3.

Here's the error we get:

mac-mini:MacOS user$ ./eclipse

java.lang.RuntimeException: Error initializing storage.

	at org.eclipse.osgi.internal.framework.EquinoxContainer.<init>(EquinoxContainer.java:68)

	at org.eclipse.osgi.launch.Equinox.<init>(Equinox.java:31)

	at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:303)

	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:239)

	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

	at java.lang.reflect.Method.invoke(Method.java:498)

	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)

	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)

	at org.eclipse.equinox.launcher.Main.run(Main.java:1519)

Caused
  by: java.io.IOException: An error occurred while locking file
"/home/user/.eclipse/org.eclipse.platform_4.6.0_1664049636_macosx_cocoa_x86_64/configuration/org.eclipse.osgi/.manager/.fileTableLock":
  "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://p302568@moe-180.gi.polymtl.ca/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.

Thank You!

-- 
Luc Lalonde, analyste
-----------------------------
Département de génie informatique:
École polytechnique de MTL
(514) 340-4711 x5049
Luc.Lalonde at polymtl.ca
-----------------------------



More information about the samba mailing list