disParity » Bug Reports

.06 crash during update

(4 posts)
  1. tahngarth
    Member

    Deleted some files on one drive, moved some on another, and added a whole new data drive (Drive E) to the system and ran an update. it crashed. here's the log.

    C:\Apps\disParity>disparity update -v
    Loading file data for F:\...1442 records loaded.
    Scanning F:\...
    Adds: 6 Moves: 0 Deletes: 0
    Loading file data for G:\...2342 records loaded.
    Scanning G:\...
    Adds: 2 Moves: 0 Deletes: 0
    Loading file data for H:\...210 records loaded.
    Scanning H:\...
    Adds: 0 Moves: 0 Deletes: 3
    Loading file data for I:\...175 records loaded.
    Scanning I:\...
    Adds: 0 Moves: 0 Deletes: 0
    Loading file data for J:\...203 records loaded.
    Scanning J:\...
    Adds: 0 Moves: 0 Deletes: 3
    Loading file data for L:\MOVIES & DVDs...48 records loaded.
    Scanning L:\MOVIES & DVDs...
    Adds: 0 Moves: 0 Deletes: 0
    Loading file data for N:\ANIME...1629 records loaded.
    Scanning N:\ANIME...
    Adds: 0 Moves: 0 Deletes: 0
    Loading file data for R:\...114318 records loaded.
    Scanning R:\...
    Adds: 2 Moves: 0 Deletes: 0
    Loading file data for S:\Anime...518 records loaded.
    Scanning S:\Anime...
    Adds: 0 Moves: 0 Deletes: 0
    Scanning E:\...
    Adds: 19 Moves: 0 Deletes: 0
    Processing deletes...
    Removing H:\\\HDTV\MOVIES-x264\American Gangster\folder.jpg...

    Unhandled Exception: System.ArgumentOutOfRangeException: Index was out of range.
    Must be non-negative and less than the size of the collection.
    Parameter name: index
    at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argu
    ment, ExceptionResource resource)
    at System.ThrowHelper.ThrowArgumentOutOfRangeException()
    at Disparity.DataPath.ReadFileData(UInt32 block, Byte[] data)
    at Disparity.Program.Update()
    at Disparity.Program.Main(String[] args)

    Removed the new drive from the config file, ran update and it completely successfully. Added the drive back, and it also updated successfully. Ran one last time and it successfully found no changes.

    Posted 6 years ago #
  2. Roland
    Roland

    Oops, changing the config.txt file like this after creating the snapshot isn't supported. I should have mentioned this in the readme. You can't add a new drive or remove an old one and then do an update. It might appear to work in some cases, or work "accidentally", but this is NOT checked for and I would assume that disParity probably didn't do the right thing, even if it completed without errors. I would either recreate your snapshot, or at least try a test recovery to see if it can recover one of the larger drives without hash failures.

    Currently if you add or remove a drive you have to recreate the snapshot afterward.

    Handling this situation correctly during an update is definitely on the To Do list.

    Posted 6 years ago #
  3. tahngarth
    Member

    Yeah, good thing to know. I'll just recreate after I finish moving stuff around, I'll be moving at least one more drive into the parity tomorrow. So I would guess that altering a path is bad too? So going from S:\Anime to S:\?

    Posted 6 years ago #
  4. Roland
    Roland

    Altering an existing path...did not explicitly try to handle that case...let me think. No, probably would not work correctly in that case either.

    Posted 6 years ago #

RSS feed for this topic

Reply

You must log in to post.