CONFIG_BTRFS_FS_CHECK_INTEGRITY: Btrfs with integrity check tool compiled in (DEPRECATED)

General informations

The Linux kernel configuration item CONFIG_BTRFS_FS_CHECK_INTEGRITY has multiple definitions:

Btrfs with integrity check tool compiled in (DEPRECATED) found in fs/btrfs/Kconfig

The configuration item CONFIG_BTRFS_FS_CHECK_INTEGRITY:

• prompt: Btrfs with integrity check tool compiled in (DEPRECATED)
• type: bool
• depends on: CONFIG_BTRFS_FS
• defined in fs/btrfs/Kconfig
• found in Linux kernels: 6.6

Help text

This feature has been deprecated and will be removed in 6.7.

Adds code that examines all block write requests (including writes of the super block). The goal is to verify that the state of the filesystem on disk is always consistent, i.e., after a power-loss or kernel panic event the filesystem is in a consistent state.

If the integrity check tool is included and activated in the mount options, plenty of kernel memory is used, and plenty of additional CPU cycles are spent. Enabling this functionality is not intended for normal use.

In most cases, unless you are a btrfs developer who needs to verify the integrity of (super)-block write requests during the run of a regression test, say N

Btrfs with integrity check tool compiled in (DANGEROUS) found in fs/btrfs/Kconfig

The configuration item CONFIG_BTRFS_FS_CHECK_INTEGRITY:

• prompt: Btrfs with integrity check tool compiled in (DANGEROUS)
• type: bool
• depends on: CONFIG_BTRFS_FS
• defined in fs/btrfs/Kconfig
• found in Linux kernels: 3.3–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.5

Help text

Adds code that examines all block write requests (including writes of the super block). The goal is to verify that the state of the filesystem on disk is always consistent, i.e., after a power-loss or kernel panic event the filesystem is in a consistent state.

If the integrity check tool is included and activated in the mount options, plenty of kernel memory is used, and plenty of additional CPU cycles are spent. Enabling this functionality is not intended for normal use.

In most cases, unless you are a btrfs developer who needs to verify the integrity of (super)-block write requests during the run of a regression test, say N

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: