Skip to content
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

Doc: scrub: explain unverified #200

Closed
kdave opened this issue Sep 2, 2019 · 4 comments
Closed

Doc: scrub: explain unverified #200

kdave opened this issue Sep 2, 2019 · 4 comments
Labels
docs Changes in documentation or help text
Milestone

Comments

@kdave
Copy link
Owner

kdave commented Sep 2, 2019

There was a question posted by Bobpaul on wiki, this is a duplicate for tracking purposes.

I'm having troubling finding an explanation for the different error classes in the scrub status output. For example: recently I had a disk drop out during usage. I powered off the system, fixed the connection, and btrfs resumed using the disk. I ran a scrub with -Bd and the disk that had been disconnected showed the following error summary:

Error summary:    verify=68082 csum=9499110
  Corrected:      9567192
  Uncorrectable:  0
  Unverified:     6592400
WARNING: errors detected during scrubbing, corrected

Corrected and Uncorrectable are self-explanatory. But what are unverified errors?

@CyberShadow
Copy link
Contributor

I found this, does it help?

btrfs-progs/ioctl.h

Lines 143 to 146 in 9a85732

__u64 unverified_errors; /* # of occurrences where a read for a
* full (64k) bio failed, but the re-
* check succeeded for each 4k piece.
* Intermittent error. */

@kdave
Copy link
Owner Author

kdave commented Sep 4, 2019

Yeah that's it. I don't know why this was added, it's kind of low-level detail how the data are read. And unverified is quite confusing.

@kdave kdave added this to the v5.2.2 milestone Sep 4, 2019
@CyberShadow
Copy link
Contributor

The relevant kernel code has some more-likely-sounding explanations in a comment:

https://github.com/kdave/btrfs-devel/blob/089cf7f6ecb266b6a4164919a2e69bd2f938374a/fs/btrfs/scrub.c#L950-L957

@kdave kdave modified the milestones: v5.2.2, v5.3 Sep 9, 2019
kdave pushed a commit that referenced this issue Sep 12, 2019
Switch backend to docbook5 for asciidoctor and disable validation as v5
does not use DTBs.

Pull-request: #200
Iissue: #201
Signed-off-by: Dimitri John Ledkov <[email protected]>
Signed-off-by: David Sterba <[email protected]>
@kdave kdave added doc:ok and removed doc:needed labels Sep 12, 2019
@kdave kdave modified the milestones: v5.3, v.5.3.2 Oct 24, 2019
@kdave kdave modified the milestones: v5.3.2, v5.4.1 Dec 3, 2019
@kdave kdave modified the milestones: v5.4.1, v5.4.2 Jan 9, 2020
@kdave kdave modified the milestones: v5.4.2, v5.5 Mar 4, 2020
@kdave kdave modified the milestones: v5.6, v5.6.1 Apr 6, 2020
@kdave kdave modified the milestones: v5.6.1, v5.6.2 May 7, 2020
@kdave kdave modified the milestones: v5.6.2, v5.7.1 Jul 2, 2020
@kdave kdave removed the doc:needed label Oct 2, 2020
@kdave kdave modified the milestones: v5.7.1, v5.9.1 Oct 23, 2020
@kdave kdave added the bug label Dec 1, 2020
@kdave kdave modified the milestones: v5.9.1, v5.10.1 Jan 18, 2021
@kdave kdave modified the milestones: v5.10.1, v5.10.2 Feb 12, 2021
@kdave kdave added docs Changes in documentation or help text and removed bug labels Feb 12, 2021
@kdave kdave removed this from the v5.10.2 milestone Mar 5, 2021
@kdave kdave added this to the v6.3 milestone Apr 19, 2023
@kdave
Copy link
Owner Author

kdave commented Apr 19, 2023

Fixed in devel.

@kdave kdave closed this as completed Apr 19, 2023
kdave added a commit that referenced this issue Apr 19, 2023
Move ionice options, add example output of status with explanation.

Issue: #200
Signed-off-by: David Sterba <[email protected]>
kdave added a commit that referenced this issue Apr 25, 2023
Move ionice options, add example output of status with explanation.

Issue: #200
Signed-off-by: David Sterba <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Changes in documentation or help text
Projects
None yet
Development

No branches or pull requests

2 participants