mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #1052] Question: Can't set up ArchiveBox DB on a virtio mount that doesn't support FSYNC (sqlite3.OperationalError: disk I/O error) #659
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#659
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rebane2001 on GitHub (Nov 22, 2022).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1052
Describe the bug
Trying to set up ArchiveBox on a virtio mount results in an error (
sqlite3.OperationalError: disk I/O error).Screenshots or log output
fstab of the affected mount:
archivebox init logs:
ArchiveBox version
@pirate commented on GitHub (Jun 13, 2023):
Sorry for the late response, unfortunately we don't support saving the SQLite DB on a filesystem that doesn't support FSYNC at the moment (as it can cause data loss when running multiple ArchiveBox commands at once).
You can find more information here: https://github.com/ArchiveBox/ArchiveBox/wiki/Security-Overview#filesystem
There is an undocumented footgun provided if you're willing to accept possible data loss when running multiple archivebox instances in parallel: set
archivebox config ENFORCE_ATOMIC_WRITES=Falsehttps://github.com/ArchiveBox/ArchiveBox/blob/dev/archivebox/config.py#L87.Comment back here if you're still having problems and I can re-open the issue :)