Sebastian Sdorra
Sebastian Sdorra
Corresponding issue from the crowd plugin: https://github.com/soudmaijer/scm-crowd-plugin/issues/16
Thanks for the report, we will have a look.
This is really strange, i can't reproduce the problem. Could you try the same without a separate volume for the home directory?
Have you checked the filesystem (`ext4 fsck`)? Perhaps there is something broken on the os side.
Could you enable trace logging for svnkit, reproduce the issue and post the log output? Enable svnkit trace logging: ```bash # get the default logging xml docker run --rm --entrypoint=/bin/cat...
Ok, this looks really strange. It looks like the problem is not the filesystem at /var/lib/scm, it seems that the problem is that `flock` is used for like locking instead...
Could you please install the script plugin, execute the following script (Administration->Scripts) and post the output? ```groovy println com.sun.jna.Native.class.getProtectionDomain().getCodeSource() ```
Could you try set the environment variable `XDG_CACHE_HOME` to `/var/cache/scm/work`?
Ok, could you try to remove the `XDG_CACHE_HOME` environment variable, rename the `/var/lib/scm/.cache` directory to `/var/lib/scm/possibly-broken-cache` and check again?
Is the exception above after the container was restarted or before?