SQlite3 virtiofs mmap

Incus
3

Thank you very much already for considering the issue I am raising.

Some partial answers:

  • dmesg does not show any information/error when running the .dump on the database;
  • the incus_raid5 pool is a zfs storage pool created by the following commands (FYI):
    • the evo970 lvm VG is composed of 4 partitions on 4 different NVME devices;
    • lvcreate -n incus_raid5 --type raid5 -i 3 -L 384GiB evo970;
    • incus storage create incus_raid5 zfs source=/dev/evo970/incus_raid5;
  • the filesystem used is virtiofs, running the command mount in the VM gives:
    • ... incus_sqlite on /mnt type virtiofs (rw,relatime) ...

As you suggested, I tried the io.bus=9p option for the sqlite custom disk device but it is not automounted anymore. There is a message virtio-fs: tag <incus_sqlite> not found early in the dmesg (I guess this is to be expected). I did check for the 9p tag incus_sqlite can indeed be found in the file /sys/bus/virtio/drivers/9pnet_virtio/virtio9/mount_tag.

However, the command mount -t 9p incus_sqlite /mnt fails this way:

root@test-sqlite:~# mount -t 9p incus_sqlite /mnt/ -o trans=virtio
mount: /mnt: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program.
       dmesg(1) may have more information after failed mount system call.

and dmesg shows no new information. Same if I simply run mount -t 9p incus_sqlite /mnt/ instead, ie w/o the option.

I will now try a different storage pool driver…

Thx again