Skip to content

--init-csum-tree requires old checksum which defeats the purpose of using it #656

Open
@tribbloid

Description

@tribbloid

Full log:

$ sudo btrfs check --init-csum-tree /dev/nvme0n1p7
Creating a new CRC tree
WARNING:

	Do not use --repair unless you are advised to do so by a developer
	or an experienced user, and then only after having accepted that no
	fsck can successfully repair all types of filesystem corruption. Eg.
	some software or hardware bugs can fatally damage a volume.
	The operation will start in 10 seconds.
	Use Ctrl-C to stop it.
10 9 8 7 6 5 4 3 2 1
Starting repair.
Opening filesystem to check...
checksum verify failed on 24708644864 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 24708644864 wanted 0x00000000 found 0xb6bde3e4
checksum verify failed on 24708644864 wanted 0x00000000 found 0xb6bde3e4
bad tree block 24708644864, bytenr mismatch, want=24708644864, have=0
ERROR: cannot read chunk root
ERROR: cannot open file system

As its name suggests, --init-csum-tree is used to rebuild checksum tree from raw data without any verification (which will be discarded and rebuilt), instead, it complained about checksum verify failed, which makes this option close to being useless

Metadata

Metadata

Assignees

No one assigned

    Labels

    docsChanges in documentation or help text

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions