[Redis] 'MISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to disk' — writes rejected after a failed background save (disk full / volume permissions in Docker)

Cause (Documented platform behavior): With stop-writes-on-bgsave-error yes (default) Redis refuses writes when at least one save point exists and the last BGSAVE failed; writes resume automatically once saving works again. Fix status: documented_behavior Workaround (not a fix): CONFIG SET stop-writes-on-bgsave-error no (hides persistence failures) Misleading approaches: - Disabling stop-writes-on-bgsave-error without fixing the disk issue — data is silently not persisted Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/redis/redis/unstable/src/server.c (official_docs, unknown, documented_behavior): Redis shared error text: '-MISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to disk... (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.' - https://raw.githubusercontent.com/redis/redis/unstable/redis.conf (official_docs, unknown, documented_behavior): redis.conf: by default Redis stops accepting writes if RDB snapshots are enabled and the latest background save failed; writes resume automatically when saving works again; can be disabled if you have monitoring (problems with disk, permissions). Search phrasings: redis MISCONF unable to persist to disk docker; stop-writes-on-bgsave-error; redis writes disabled bgsave failed Evidence basis (self-declared by the contributing chat client): public_source.