search

Chronial / snapraid-runner

Python script for SnapRAID cronjobs
MIT License
302 stars 96 forks source link

Auto fix errors after scrub #28

Closed XDGFX closed 3 years ago

XDGFX commented 4 years ago

Would it make sense to auto run sudo snapraid -e fix after a scrub detects an error? It could be implemented easily, I just wondered if there's reasoning against it being automatic? I seem to get an error almost every other sync, so would be nice if it automatically corrected them.

Chronial commented 4 years ago

I am strongly opposed to doing any kind of automatic fix. If a scrub detects an error, something went wrong and needs investigating. How do you get an error on almost every sync?

XDGFX commented 4 years ago

This is the typical error I get

25782', diff bits 65/128
2020-03-05 06:40:24,240 [OUTERR] Data error in file
'/media/mfs-rainbow-lorikeet/Projects/Video/In Work/Archive/Ski Trip MMXV
Footage/Hero 3+/Day 5/GOPR1105.MP4' at position '4275', diff bits 62/128
2020-03-05 09:33:14,660 [OUTERR] DANGER! Unexpected data errors! The
failing blocks are now marked as bad!
2020-03-05 09:33:14,665 [OUTERR] Use 'snapraid status' to list the bad
blocks.
2020-03-05 09:33:14,666 [OUTERR] Use 'snapraid -e fix' to recover.

On Wed, 4 Mar 2020, 8:05 pm Christian Fersch, notifications@github.com wrote:

I am strongly opposed to doing any kind of automatic fix. If a scrub detects an error, something went wrong and needs investigating. How do you get an error on almost every sync?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Chronial/snapraid-runner/issues/28?email_source=notifications&email_token=AD4ZG4CAGMF377XO44ONRQ3RF2X6JA5CNFSM4K73YNVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENZ73DA#issuecomment-594804108, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD4ZG4C75OWI3OP4MUJWYRLRF2X6JANCNFSM4K73YNVA .