mirror of
https://github.com/kdave/btrfs-progs
synced 2025-02-25 22:40:38 +00:00
83120248d0
Adds a test that btrfs check doesn't flag a file extent in the log tree as
an error because of no corresponding csum entry, if the file extent is
actually an explicit hole. See commit f6dc0e86.
The log tree in hole.img.xz:
log tree key (TREE_LOG ROOT_ITEM 5)
leaf 5373952 items 3 free space 15981 generation 7 owner TREE_LOG
leaf 5373952 flags 0x1(WRITTEN) backref revision 1
checksum stored 091c2f32
checksum calced 091c2f32
fs uuid 70d417f0-0173-49ca-bdf1-b789a798974d
chunk uuid b7ec3806-ea09-4f18-a5ef-126a2d79105e
item 0 key (257 INODE_ITEM 0) itemoff 16123 itemsize 160
generation 7 transid 7 size 4096 nbytes 0
block group 0 mode 100644 links 1 uid 0 gid 0 rdev 0
sequence 1 flags 0x0(none)
atime 1721050040.375996658 (2024-07-15 14:27:20)
ctime 1721050040.375996658 (2024-07-15 14:27:20)
mtime 1721050040.375996658 (2024-07-15 14:27:20)
otime 0.2820488960 (1970-01-01 01:00:00)
item 1 key (257 INODE_REF 256) itemoff 16109 itemsize 14
index 2 namelen 4 name: file
item 2 key (257 EXTENT_DATA 0) itemoff 16056 itemsize 53
generation 7 type 1 (regular)
extent data disk byte 0 nr 0
extent data offset 0 nr 4096 ram 4096
extent compression 0 (none)
Signed-off-by: Mark Harmstone <maharmstone@fb.com>
[ Move the image to 065-valid-log tree ]
Signed-off-by: Qu Wenruo <wqu@suse.com>
14 lines
215 B
Bash
Executable File
14 lines
215 B
Bash
Executable File
#!/bin/bash
|
|
#
|
|
# Verify that check doesn't cause false alerts on various valid log trees
|
|
|
|
source "$TEST_TOP/common" || exit
|
|
|
|
check_prereq btrfs
|
|
|
|
check_image() {
|
|
run_check "$TOP/btrfs" check "$1"
|
|
}
|
|
|
|
check_all_images
|