disParity » General Discussion

Verify command

(6 posts)
  • Started 1 year ago by BloodlustMAC
  • Latest reply from BloodlustMAC
  1. BloodlustMAC
    Member

    I did a scan all ... update with no issues.

    I did a verify command to see what it would do ... and found the disparity log file with:

    28/04/2014 19:37:02 Beginning Verify
    28/04/2014 19:37:02 Block 5 does not match
    28/04/2014 19:37:02 Block 5 contains data from the following file or files (each file will only be reported once per verify pass):
    28/04/2014 19:37:02 <file a>
    28/04/2014 19:37:02 <file b>
    28/04/2014 19:37:02 <file c>
    28/04/2014 19:37:02 <file d>
    28/04/2014 19:37:02 <file e>
    28/04/2014 19:37:02 <file f>
    28/04/2014 19:37:02 <file g>
    28/04/2014 19:37:02 <file h>
    28/04/2014 19:37:02 Block 5 repaired.

    Implying issues with seemingly valid data.
    What has been repaired !?

    Could you explain what this means !?

    Posted 1 year ago #
  2. Roland
    Roland

    Under normal circumstances, this should never occur. The only reasons that Verify would find an invalid block are either a) a bug in disParity (certainly possible although I'm not currently aware of any that would cause this) or b) a corrupt file.

    When Verify finds a bad block, it "repairs" it by re-calculating the block from scratch based on all the files overlapping in that block. So, in theory, your backup should be fixed now.

    Posted 1 year ago #
  3. BloodlustMAC
    Member

    This is worrying as the data which was backed up was not in anyway flagged with issues.

    I did do a full hash check recently ... with no issues.

    So I find it strange to see these in the log.

    ... especially when doing a scan all ... update all.

    Posted 1 year ago #
  4. Roland
    Roland

    I agree, it's worrying. As I said, it should not normally happen, and I can't explain why you are getting the error. I run Verify routinely myself just to make sure all is well, and I don't get errors. So, it's a mystery.

    Are you getting LOTS of block errors, or only a few?

    Posted 1 year ago #
  5. BloodlustMAC
    Member

    21 million files in (going to take 4 days to verify) from 44 million, had 196 error found with fixes.

    There are four sections affecting four groups of files (183, 10, 1, 2).

    Does not appear to be related to blocks, filenames or anything else I can see.

    Posted 1 year ago #
  6. BloodlustMAC
    Member

    Completed only 196 errors found ... now all up to date ... hopefully.

    Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.