Skip to content

sqlite3.OperationalError: disk I/O error #11

Description

@loraine-gueguen

Do you get error "sqlite3.OperationalError: disk I/O error" when the askomics volume is stored on the NFS filesystem ?

I have this error when the volume is stored on the NFS file system in the askomics, celery_askomics, celerybeat_askomics services :
- ../../../finalresult/phaeoaskomics_docker-data/askomics:/tmp/askomics

In docker inspect flaskomics-docker-compose_standalone-askomics-1 output:

        "Mounts": [
            {
                "Type": "bind",
                "Source": "/shared/projects/phaeoaskomics/finalresult/phaeoaskomics_docker_data/askomics",
                "Destination": "/tmp/askomics",
                "Mode": "rw",
                "RW": true,
                "Propagation": "rprivate"
            }
        ],

And:

$ stat -f -c %T /shared/projects/phaeoaskomics/finalresult/phaeoaskomics_docker_data/askomics
nfs

The error does not happen when the volume is stored locally:
- /tmp/askomics:/tmp/askomics

$ stat -f -c %T /tmp/askomics
ext2/ext3

In docker inspect flaskomics-docker-compose_standalone-askomics-1 output:

        "Mounts": [
            {
                "Type": "bind",
                "Source": "/tmp/askomics",
                "Destination": "/tmp/askomics",
                "Mode": "rw",
                "RW": true,
                "Propagation": "rprivate"
            }
        ],

Works fine as well with a named volume stored in /var/lib/docker/volumes.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions