disParity » General Discussion

Auto Update nearly cost me a lot of data!

(4 posts)
  1. ajiau
    Member

    I just logged onto my server to see one of my 6 drives has failed with an "IO Error". Disparity v0.41 - which is always running - had interpret this failure as a delete of all 9000 files, and was happily ticking away updating the parity set! I cancelled the update, rebooted the server and the drive is back up. Disparity is now updating the parity set with the few hundred files it had just removed!

    There needs to be clear code in the update mechanism to distinguish between files being missing and IO errors. Not quite sure how this would be achieved, but it's important!

    Posted 11 months ago #
  2. Roland
    Roland

    Hmmm, I wish I knew how this happened. Any sort of I/O error on any drive is supposed to immediately cancel the update. All the update code paths are wrapped in exception handlers that do this.

    Failing drives are tough because if they haven't failed completely, they can start to fail in all sorts of weird and subtle ways that I have no way to reproduce under the debugger.

    Did disParity actually log an I/O error? If so can you post the log snippet?

    Posted 11 months ago #
  3. ajiau
    Member

    I found the exact part of the log! Here you go:

    6/11/2014 4:06:16 PM Application launched (version 0.41)
    6/11/2014 4:08:43 PM Scanning E:\array...
    6/11/2014 4:08:43 PM Checking for upgrade...
    6/11/2014 4:08:44 PM Scanning F:\array...
    6/11/2014 4:08:46 PM Current version: 0.41 Latest version: 0.41
    6/11/2014 4:08:46 PM Scanning G:\array...
    6/11/2014 4:08:47 PM Scanning I:\array...
    6/11/2014 4:08:47 PM Scanning H:\array...
    6/11/2014 4:08:47 PM Scanning J:\array...
    6/11/2014 4:08:50 PM Scan of E:\array complete. Found 1910 files Adds: 0 Deletes: 0 Moves: 0 Edits: 0 Ignored: 0
    6/11/2014 4:08:56 PM Scan of G:\array complete. Found 6692 files Adds: 0 Deletes: 0 Moves: 0 Edits: 0 Ignored: 0
    6/11/2014 4:09:00 PM Scan of F:\array complete. Found 7550 files Adds: 0 Deletes: 0 Moves: 0 Edits: 0 Ignored: 0
    6/11/2014 4:09:07 PM Scan of H:\array complete. Found 6797 files Adds: 0 Deletes: 0 Moves: 0 Edits: 0 Ignored: 0
    6/11/2014 4:09:19 PM Warning: Could not enumerate subdirectories of J:\array\TV2: The request could not be performed because of an I/O device error.

    6/11/2014 4:09:19 PM Scan of J:\array complete. Found 0 files Adds: 0 Deletes: 9818 Moves: 0 Edits: 0 Ignored: 0
    6/11/2014 4:09:26 PM Scan of I:\array complete. Found 28887 files Adds: 0 Deletes: 0 Moves: 0 Edits: 0 Ignored: 0
    6/11/2014 4:09:26 PM Beginning Scan
    6/11/2014 4:09:26 PM Scan complete (operation took 42.671 seconds)
    6/11/2014 4:14:26 PM Beginning Update
    6/11/2014 4:14:26 PM Free space on parity drive: 28.1 GB (30183899136 bytes)
    6/11/2014 4:14:27 PM Removing J:\array\TV2\[NAME_REDACTED].avi...
    6/11/2014 4:17:06 PM K:\files6.dat saved in 142ms
    6/11/2014 4:17:06 PM Removing J:\array\TV2\[NAME_REDACTED].avi...
    6/11/2014 4:18:48 PM K:\files6.dat saved in 161ms
    [Proceeds to continue removing 9818 files from Parity]

    Posted 11 months ago #
  4. Roland
    Roland

    Thanks for the log snippet, it was very helpful. I think I've identified how this was able to happen. I will roll the fix into the next beta update.

    Posted 11 months ago #

RSS feed for this topic

Reply

You must log in to post.