jasonwittyandClaude Opus 5
91d96eb17a
LimeSurvey was never in this repo, and its two PVCs used the k3s local-path
StorageClass: both volumes were pinned to rpi-worker-3's local disk with
persistentVolumeReclaimPolicy: Delete. That put the survey data on a single
SD-backed node with no replication, where deleting the PVC would destroy it.
Both volumes now live on gvolume0 under /mnt/gvolume0/limesurvey/{app,db},
with Retain, matching the pattern used by vaultwarden and tududi. Migrated
2026-09-21 via mysqldump/restore; verified identical afterwards (3 surveys,
742 responses, 2 users, 17 questions, 60 tables).
db-config.yaml is required, not optional: InnoDB's defaults assume a local
POSIX filesystem, and on a GlusterFS FUSE mount native AIO is unavailable and
O_DIRECT unreliable. Without innodb_use_native_aio=0 and
innodb_flush_method=fsync, MariaDB either fails to start or risks corruption.
A nightly dump to /mnt/gvolume0/limesurvey/backups (14 day retention) is
included -- a volume survives losing a node, but a logical dump also survives
corruption, a bad upgrade and mistaken deletes.
The old local-path PVCs (limesurvey-db-data, limesurvey-uploads) are
deliberately left in place as a rollback and are not managed here.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
16 lines
527 B
YAML
16 lines
527 B
YAML
# InnoDB defaults assume a local POSIX filesystem. The datadir now lives on a
|
|
# GlusterFS FUSE mount, where native async I/O is unavailable and O_DIRECT is
|
|
# unreliable -- without these, MariaDB either fails to start ("Failed to
|
|
# initialize AIO") or risks corruption. Keep these with the gluster PV.
|
|
apiVersion: v1
|
|
kind: ConfigMap
|
|
metadata:
|
|
name: limesurvey-db-config
|
|
namespace: limesurvey
|
|
data:
|
|
99-gluster.cnf: |
|
|
[mariadb]
|
|
innodb_use_native_aio = 0
|
|
innodb_flush_method = fsync
|
|
innodb_file_per_table = 1
|