Error: Unexpected error disk I/O error #32571

Activity

1. github-actions

   assigned

   kitlangton

   on Jun 16, 2026
2. ericzhan-ops commented on Jul 3, 2026

   

   ericzhan-ops

   on Jul 3, 2026

   More actions

   Upgrade host libseccomp package >= 2.5.2 version
3. jychoi-hpc commented on Aug 12, 2026

   

   jychoi-hpc

   on Aug 12, 2026

   Last edited by jychoi-hpc

   More actions

   I am also getting the same error. I believe I have libseccomp 2.5.3 in my system. Is there any way to debug this error? Any way to print verbose message? Here is my output:

   $ opencode --print-logs --log-level DEBUG  run hello
   Error: Unexpected error
   
   disk I/O error
   

   Using opencode version 1.18.16:

   $ opencode --version
   1.18.16
   
4. chrissound commented on Aug 12, 2026

   

   chrissound

   on Aug 12, 2026

   Author

   More actions

   it's likely due to running on a vm with a 9p shared filesystem...
5. jychoi-hpc commented on Aug 12, 2026

   

   jychoi-hpc

   on Aug 12, 2026

   Last edited by jychoi-hpc

   More actions

   Thanks for the info. That makes sense. I’m trying to run this within a SLURM job allocation on Frontier at ORNL. Is there a workaround for this?
6. chrissound commented on Aug 12, 2026

   

   chrissound

   on Aug 12, 2026

   Author

   More actions

   you can try set $HOME to a place that isn't under a 9p mount
7. jychoi-hpc commented on Aug 13, 2026

   

   jychoi-hpc

   on Aug 13, 2026

   More actions

   @chrissound, thank you for the information. Yes, $HOME works.

   Based on your suggestion, I found that setting the OpenCode database location (using the OPENCODE_DB environment variable) to a path that is not under a 9p mount works. For example:

   OPENCODE_DB=/dir/to/somewhere/opencode.db opencode run hello
   
8. neriousy commented on Oct 1, 2026

   

   neriousy

   on Oct 1, 2026

   Member

   More actions

   Closing this one. The error comes from the environment, not OpenCode: SQLite can't reliably lock its database on a 9p shared filesystem. The workaround is to put the database on a local disk, either with the OPENCODE_DB environment variable or by pointing $HOME at a non-9p location.

   If you see disk I/O error with the database on a local filesystem, please open a new issue.
9. neriousy

   closed this as not plannedon Oct 1, 2026
10. chrissound commented on Oct 1, 2026

    

    chrissound

    on Oct 1, 2026

    Author

    More actions

    Ideally you should inform the user of this limitation rather than showing a generic error and having them needing to find this exact issue..
11. neriousy commented on Oct 1, 2026

    

    neriousy

    on Oct 1, 2026

    Member

    More actions

    Yeah you're right - i will try to look into it how to better show the error, that one is probably a generic sqlite error returned from upstream

    👍React with 👍1Reacted by Chris Stryczynski