edupv Posted June 18, 2018 Posted June 18, 2018 CONFIG_BTRFS_FS_CHECK_INTEGRITY is not enabled in config. When I tried to enable it in the armbian build system, I saw the word "DANGEROUS". Is this an unstable (or dangerous) feature ? Should I enabled it and use it ? if not, how to ensure data integrity ?
zador.blood.stained Posted June 18, 2018 Posted June 18, 2018 On 6/18/2018 at 2:59 AM, edupv said: Is this an unstable (or dangerous) feature ? Should I enabled it and use it ? Expand It also has a description config BTRFS_FS_CHECK_INTEGRITY bool "Btrfs with integrity check tool compiled in (DANGEROUS)" depends on BTRFS_FS help 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 On 6/18/2018 at 2:59 AM, edupv said: if not, how to ensure data integrity ? Expand You can read the btrfs FAQ to start with
edupv Posted June 18, 2018 Author Posted June 18, 2018 On 6/18/2018 at 9:29 AM, zador.blood.stained said: It also has a description config BTRFS_FS_CHECK_INTEGRITY bool "Btrfs with integrity check tool compiled in (DANGEROUS)" depends on BTRFS_FS help 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 You can read the btrfs FAQ to start with Expand Thanks for your explanation.
Recommended Posts