You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, still having an unrecoverable crash issue intermittently. I cannot restart riofs without first running an umount on the directory. I managed to harvest a verbose log right before a crash; not sure it's of any help:
Hello,
without any additional logs I can't tell you for sure what happened.
This log says that for some reason "Mountpoint /d1/s2s/s3/optimus does not exist".
Could you please check if any other running script removes this mount or folder?
Hi, how could I get some additional logs? This verbose setting writes GB's to disk.
The mount point exists, it just gets tied up by RioFS somehow.
Once it's finally crashed, I cannot restart RioFS until I umount. However doing an umount too soon; gives this:
umount: /d1/s2s/s3/optimus: target is busy
(In some cases useful info about processes that
use the device is found by lsof(8) or fuser(1).)
Hi, still having an unrecoverable crash issue intermittently. I cannot restart riofs without first running an umount on the directory. I managed to harvest a verbose log right before a crash; not sure it's of any help:
The text was updated successfully, but these errors were encountered: