I was opening a bgi file directly from the dxfuse mounted filesystem with a JupyterLab instance. I soon started getting "transport endpoint is not connected" errors. After that, nothing would load from /mnt/project?not only this file, but any other file. This seems like a bug. Is there a workaround (for example, a way to restart dxfuse)?
I would like to bring this issue up again. I am mounting the dispensed imputed UKB genetic data in a cloud-workstation, but after 45mins of processing a .bgen file, I get a file read error, saying ‘Transport endpoint is not connected’, due to the dx-fuse mount breaking.
Simply remounting the directory is not an option as the progress made is lost. Is there a way to stop dx-fuse mounts breaking?
I am using the dxfuse-linux v1.4.0 release from GitHub.
Comments
2 comments
Hi James ?,
I remember that some time ago I was able to remount the /mnt/project and I documented it here: https://community.dnanexus.com/s/question/0D5t000003vAWYxCAO/it-seems-that-the-recently-dx-uploaded-files-does-not-show-up-on-mntproject-until-i-restart-the-whole-jupyter-lab-vm
Hope this helps and if not, I think you can report it to ukbiobank-support@dnanexus.com.
I would like to bring this issue up again. I am mounting the dispensed imputed UKB genetic data in a cloud-workstation, but after 45mins of processing a .bgen file, I get a file read error, saying ‘Transport endpoint is not connected’, due to the dx-fuse mount breaking.
Simply remounting the directory is not an option as the progress made is lost. Is there a way to stop dx-fuse mounts breaking?
I am using the dxfuse-linux v1.4.0 release from GitHub.
Any advice is much appreciated.
Please sign in to leave a comment.