-
Notifications
You must be signed in to change notification settings - Fork 149
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
Server reports all pages with bad checksum when first page of a file is corrupted #1864
Comments
amadio
added a commit
to amadio/xrootd
that referenced
this issue
Dec 14, 2022
Merged
amadio
added a commit
to amadio/xrootd
that referenced
this issue
Dec 14, 2022
amadio
added a commit
that referenced
this issue
Dec 15, 2022
amadio
added a commit
to amadio/xrootd
that referenced
this issue
Dec 15, 2022
amadio
added a commit
to amadio/xrootd
that referenced
this issue
Dec 15, 2022
amadio
added a commit
to amadio/xrootd
that referenced
this issue
Dec 16, 2022
amadio
added a commit
to amadio/xrootd
that referenced
this issue
Dec 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This bug was discovered by @simonmichal, and can be reproduced by applying the change below on the client, then trying to copy a file with xrdcp:
The change above just sets the checksum of the first page to 0, but the server reports all pages having a bad checksum. After some debugging, we reached the conclusion that there is a bug in
XrdOucPgrwUtils::csVer
(shown below):When
if (pgNum >=0)
is entered,dInfo.csval
is updated, but the pointerdInfo.data
remains the same, so subsequent pages are checked against the wrong checksum, which results in bad offsets being reported for all pages.The text was updated successfully, but these errors were encountered: