{
    "mode": "info",
    "parameter": "VERITYTAB",
    "section": "",
    "url": "https://www.chedong.com/phpMan.php/info/VERITYTAB/json",
    "generated": "2026-07-05T23:45:05Z",
    "synopsis": "/etc/veritytab",
    "sections": {
        "NAME": {
            "content": "veritytab - Configuration for verity block devices\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "/etc/veritytab\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "The /etc/veritytab file describes verity protected block devices that\nare set up during system boot.\n\nEmpty lines and lines starting with the \"#\" character are ignored. Each\nof the remaining lines describes one verity protected block device.\nFields are delimited by white space.\n\nEach line is in the form\n\nvolume-name data-device hash-device roothash options\n\nThe first four fields are mandatory, the remaining one is optional.\n\nThe first field contains the name of the resulting verity volume; its\nblock device is set up below /dev/mapper/.\n\nThe second field contains a path to the underlying block data device,\nor a specification of a block device via \"UUID=\" followed by the UUID.\n\nThe third field contains a path to the underlying block hash device, or\na specification of a block device via \"UUID=\" followed by the UUID.\n\nThe fourth field is the \"roothash\" in hexadecimal.\n\nThe fifth field, if present, is a comma-delimited list of options. The\nfollowing options are recognized:\n\nignore-corruption, restart-on-corruption, panic-on-corruption\nDefines what to do if a data verity problem is detected (data\ncorruption). Without these options kernel fails the IO operation\nwith I/O error. With \"--ignore-corruption\" option the corruption is\nonly logged. With \"--restart-on-corruption\" or\n\"--panic-on-corruption\" the kernel is restarted (panicked)\nimmediately. (You have to provide way how to avoid restart loops.)\n\nignore-zero-blocks\nInstruct kernel to not verify blocks that are expected to contain\nzeroes and always directly return zeroes instead. WARNING: Use this\noption only in very specific cases. This option is available since\nLinux kernel version 4.5.\n\ncheck-at-most-once\nInstruct kernel to verify blocks only the first time they are read\nfrom the data device, rather than every time. WARNING: It provides\na reduced level of security because only offline tampering of the\ndata device's content will be detected, not online tampering. This\noption is available since Linux kernel version 4.17.\n\nroot-hash-signature=\nA base64 string encoding the root hash signature prefixed by\n\"base64:\" or a path to roothash signature file used to verify the\nroot hash (in kernel). This feature requires Linux kernel version\n5.4 or more recent.\n\nnetdev\nMarks this veritysetup device as requiring network. It will be\nstarted after the network is available, similarly to\nsystemd.mount(5) units marked with netdev. The service unit to set\nup this device will be ordered between remote-fs-pre.target and\nremote-veritysetup.target, instead of veritysetup-pre.target and\nveritysetup.target.\n\nHint: if this device is used for a mount point that is specified in\nfstab(5), the netdev option should also be used for the mount\npoint. Otherwise, a dependency loop might be created where the\nmount point will be pulled in by local-fs.target, while the service\nto configure the network is usually only started after the local\nfile system has been mounted.\n\nnoauto\nThis device will not be added to veritysetup.target. This means\nthat it will not be automatically enabled on boot, unless something\nelse pulls it in. In particular, if the device is used for a mount\npoint, it'll be enabled automatically during boot, unless the mount\npoint itself is also disabled with noauto.\n\nnofail\nThis device will not be a hard dependency of veritysetup.target.\nIt'll still be pulled in and started, but the system will not wait\nfor the device to show up and be enabled, and boot will not fail if\nthis is unsuccessful. Note that other units that depend on the\nenabled device may still fail. In particular, if the device is used\nfor a mount point, the mount point itself also needs to have the\nnofail option, or the boot will fail if the device is not enabled\nsuccessfully.\n\nx-initrd.attach\nSetup this verity protected block device in the initramfs,\nsimilarly to systemd.mount(5) units marked with x-initrd.mount.\n\nAlthough it's not necessary to mark the mount entry for the root\nfile system with x-initrd.mount, x-initrd.attach is still\nrecommended with the verity protected block device containing the\nroot file system as otherwise systemd will attempt to detach the\ndevice during the regular system shutdown while it's still in use.\nWith this option the device will still be detached but later after\nthe root file system is unmounted.\n\nAll other verity protected block devices that contain file systems\nmounted in the initramfs should use this option.\n\nAt early boot and when the system manager configuration is reloaded,\nthis file is translated into native systemd units by systemd-\nveritysetup-generator(8).\n",
            "subsections": []
        },
        "EXAMPLES": {
            "content": "Example 1. /etc/veritytab example\n\nSet up two verity protected block devices. One using device blocks,\nanother using files.\n\nusr  PARTUUID=783e45ae-7aa3-484a-beef-a80ff9c19cbb PARTUUID=21dc1dfe-4c33-8b48-98a9-918a22eb3e37 36e3f740ad502e2c25e2a23d9c7c17bf0fdad2300b7580842d4b7ec1fb0fa263 auto\ndata /etc/data /etc/hash a5ee4b42f70ae1f46a08a7c92c2e0a20672ad2f514792730f5d49d7606ab8fdf auto\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "systemd(1), systemd-veritysetup@.service(8), systemd-veritysetup-\ngenerator(8), fstab(5), veritysetup(8),\n\nsystemd 249                                                       VERITYTAB(5)",
            "subsections": []
        }
    },
    "summary": "veritytab - Configuration for verity block devices",
    "flags": [],
    "examples": [
        "Example 1. /etc/veritytab example",
        "Set up two verity protected block devices. One using device blocks,",
        "another using files.",
        "usr  PARTUUID=783e45ae-7aa3-484a-beef-a80ff9c19cbb PARTUUID=21dc1dfe-4c33-8b48-98a9-918a22eb3e37 36e3f740ad502e2c25e2a23d9c7c17bf0fdad2300b7580842d4b7ec1fb0fa263 auto",
        "data /etc/data /etc/hash a5ee4b42f70ae1f46a08a7c92c2e0a20672ad2f514792730f5d49d7606ab8fdf auto"
    ],
    "see_also": [
        {
            "name": "systemd",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/systemd/1/json"
        },
        {
            "name": ".service",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/.service/8/json"
        },
        {
            "name": "generator",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/generator/8/json"
        },
        {
            "name": "fstab",
            "section": "5",
            "url": "https://www.chedong.com/phpMan.php/man/fstab/5/json"
        },
        {
            "name": "veritysetup",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/veritysetup/8/json"
        }
    ]
}