After a scrub I got in the status an absurd value for blocks scrub age:
- The oldest block was scrubbed 146 days ago, the median 55, the newest 4294967229.
How can I restore the usual 0 value?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ciao Andrea,
after a full scrub I got this message:
The oldest block was scrubbed 1 days ago, the median 1, the newest 4294967261.
No sync is in progress.
The full array was scrubbed at least one time.
No file has a zero sub-second timestamp.
No rehash is in progress or needed.
No error detected.
New ideas?
Alessandro
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The oldest block was scrubbed 1 days ago, the median 1, the newest 4294967261.
I suspect you did (Leifi's suggested) "snapraid scrub -p 100 -o 0" whereas (I believe) Andrea intended for you to do "snapraid scrub -p full". The ironically subtle difference is in the "-o 0".
--UhClem "How do I like the future?? -- Well, the future's not here yet, man."
Last edit: UhClem 2018-10-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After a scrub I got in the status an absurd value for blocks scrub age:
- The oldest block was scrubbed 146 days ago, the median 55, the newest 4294967229.
How can I restore the usual 0 value?
this may be some error code (the value is -67 for 32bit integer).
what happens if you do an additional scrub? Is the value than fine again?
No, even after many scrubs remains the same...
After many syncs and scrubs the newest scrubbed block has the same absurd value. No way to get the exact file giving this value?
How big is your largest drive? and what block size do you have in config?
biggest drive: 8.001.427.599.360 byte (7.27 TB NTFS)
block_size 256
Ok, that rules out relationship to 42 million block limit (which causes wierd progress indication during sync).
If it was my array I would try snapraid scrub -p 100 -o 0 and if it still doesn't go away I would consider rebuilding the array from scratch.
[One day ago (ie, 21 days after the first posting)] :
Is it really still the same ? Or, has your original 4294967229 actually "decreased" to [an equally absurd :) ] 4294967207 ?
\\\\\ If so ...
Well, in about 12 million years, it will be zero ... but only for one day ... then deja vu.
Sorry, I couldn't resist. \\\\\
But, seriously, I do have a promising theory, but wanted confirmation (of the daily decrement) before further investigation.
--UhClem "Welcome to the Future Fair -- a fair for all, and no fair to anybody!"
Hi,
It seems that SnapRAID wrote a scrub date in the future. This resulted in a negative time, that due integer overflow got a very high value.
A full scrub should remove that value.
I'll make a change to prevent that to happen again in future.
Ciao,
Andrea
Ciao Andrea,
after a full scrub I got this message:
The oldest block was scrubbed 1 days ago, the median 1, the newest 4294967261.
No sync is in progress.
The full array was scrubbed at least one time.
No file has a zero sub-second timestamp.
No rehash is in progress or needed.
No error detected.
New ideas?
Alessandro
I suspect you did (Leifi's suggested) "snapraid scrub -p 100 -o 0" whereas (I believe) Andrea intended for you to do "snapraid scrub -p full". The ironically subtle difference is in the "-o 0".
--UhClem "How do I like the future?? -- Well, the future's not here yet, man."
Last edit: UhClem 2018-10-05
Correct, I'll try the second option.
Ciao Andrea,
I can confirm that a
snapraid scrub -p fullsolved the problem.Grazie
Alessandro