Waxhead posted on Mon, 28 Dec 2015 00:06:46 +0100 as excerpted: > btrfs scrub status /mnt scrub status for > 2832346e-0720-499f-8239-355534e5721b > scrub started at Sun Mar 29 23:21:04 2015 and finished after > 00:01:04 > total bytes scrubbed: 1.97GiB with 14549 errors error details: > super=2 csum=14547 corrected errors: 0, uncorrectable errors: > 14547, unverified > errors: 0 > > Now here is the first worrying part... it says that scrub started at Sun > Mar 29. That is NOT true, the first scrub I did on this filesystem was a > few days ago and it claims it is a lot of uncorrectable errors. Why? > This is after all a raid6 filesystem correct?!
Hmm... The status is stored in readable plain-text files in /var/lib/ btrfs/scrub.status.*, where the * is the UUID. If you check there, the start time (t_start) seems to be in POSIX time. Is it possible you were or are running the scrub from, for instance, a rescue image that might not set the system time correctly and that falls back to, say, the date the rescue image was created, if it can't get network connectivity or some such? -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
