-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--is-reflink skips every second extent #527
Labels
Comments
This was referenced Sep 16, 2021
cebtenzzre
added a commit
to cebtenzzre/rmlint
that referenced
this issue
Sep 16, 2021
Completing the current loop iteration if the current extent is not contiguous with the last means the extent flags and file offset are updated as if the extents *were* contiguous. In general, this causes calling code to skip every second extent! Also remove a redundant write to file_offset_next that is always clobbered after the loop exits. Fixes sahib#527
cebtenzzre
added a commit
to cebtenzzre/rmlint
that referenced
this issue
Sep 28, 2021
Completing the current loop iteration if the current extent is not contiguous with the last means the extent flags and file offset are updated as if the extents *were* contiguous. In general, this causes calling code to skip every second extent! Also remove a redundant write to file_offset_next that is always clobbered after the loop exits. Fixes sahib#527
cebtenzzre
added a commit
to cebtenzzre/rmlint
that referenced
this issue
Aug 7, 2022
Completing the current loop iteration if the current extent is not contiguous with the last means the extent flags and file offset are updated as if the extents *were* contiguous. In general, this causes calling code to skip every second extent! Also remove a redundant write to file_offset_next that is always clobbered after the loop exits. Fixes sahib#527
cebtenzzre
added a commit
to cebtenzzre/rmlint
that referenced
this issue
Sep 18, 2022
Completing the current loop iteration if the current extent is not contiguous with the last means the extent flags and file offset are updated as if the extents *were* contiguous. In general, this causes calling code to skip every second extent! Also remove a redundant write to file_offset_next that is always clobbered after the loop exits. Fixes sahib#527
cebtenzzre
added a commit
to cebtenzzre/rmlint
that referenced
this issue
Feb 24, 2023
Completing the current loop iteration if the current extent is not contiguous with the last means the extent flags and file offset are updated as if the extents *were* contiguous. In general, this causes calling code to skip every second extent! Also remove a redundant write to file_offset_next that is always clobbered after the loop exits. Fixes sahib#527
intelfx
pushed a commit
to intelfx/rmlint
that referenced
this issue
Mar 9, 2023
Completing the current loop iteration if the current extent is not contiguous with the last means the extent flags and file offset are updated as if the extents *were* contiguous. In general, this causes calling code to skip every second extent! Also remove a redundant write to file_offset_next that is always clobbered after the loop exits. Fixes sahib#527
intelfx
pushed a commit
to intelfx/rmlint
that referenced
this issue
Mar 9, 2023
Completing the current loop iteration if the current extent is not contiguous with the last means the extent flags and file offset are updated as if the extents *were* contiguous. In general, this causes calling code to skip every second extent! Also remove a redundant write to file_offset_next that is always clobbered after the loop exits. Fixes sahib#527
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
rmlint --is-reflink completely skips every second extent.
Steps to reproduce
Build rmlint from the develop branch with _RM_OFFSET_DEBUG=1.
Then run these commands:
Actual result
rmlint prints "Reflink" and exits with status 0.
It compares four pairs of physical offsets, despite the files having nine extents each.
Expected result
rmlint prints "Not linked" and exits with status 11.
There should be a message like
DEBUG: Physical offsets differ at byte 102400: 673052336128<> 682882265088
.Versions
rmlint version 2.10.1 built from develop commit bdb591f with _RM_OFFSET_DEBUG=1.
The text was updated successfully, but these errors were encountered: