java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:116)
java.base/sun.nio.fs.UnixFileStore.readAttributes(UnixFileStore.java:115)
java.base/sun.nio.fs.UnixFileStore.getTotalSpace(UnixFileStore.java:122)
org.yamcs.parameter.FileStoreParameterProducer.getSystemParameters(FileStoreParameterProducer.java:96)
org.yamcs.parameter.SystemParametersService.run(SystemParametersService.java:174)
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
java.base/java.lang.Thread.run(Thread.java:829)
When unmounting a volume after starting YAMCS, it will spam the console with the above exception. My concern is if this puts this system in some unstable state.
I suspect this might be related to some of the issue we've seen in #4 and #5. I think...this needs to be investigated further.
When unmounting a volume after starting YAMCS, it will spam the console with the above exception. My concern is if this puts this system in some unstable state.
I suspect this might be related to some of the issue we've seen in #4 and #5. I think...this needs to be investigated further.