maria-discuss team mailing list archive

[Gordan Bobic <gordan.bobic@xxxxxxxxx>]

On Fri, Dec 9, 2022 at 2:43 AM Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote:

> > If you're concerned about database corruption then you need to start off
> > by having multiple copies of the data available in an online state if
> > you want to recover from corrupt data without doing a backup.
>
> completly different topic
>
> > This is
> > what ZFS does with RAID - detects which block is corrupt and then uses
> > other data blocks, including parity, to rebuild the corrupt block.
>
> completly different layers
>
> > MariaDB isn't designed for that. I'm not even sure if there is any
> > database that's designed for that, including SQL Server (see below for
> > more.)
>
> the topic was "Some of us run MariaDB on file systems that do their own
> block checksumming, and thus run innodb_checksum_algorithm=none" where
> you mix two completly independent layers and now we have two morons

Virtually all data corruption that occurs happens in the disk layer,
not the database internals layer. This is the reality you seem to be
struggling to grasp.
If address the problem of corruption in the disk layer, the usefulness
of additionally checking in a place that is only useful for internals
debugging is vanishingly narrow.