Verify failure: now what?

This has happened to me 3 times now.

1. Create the RAID.
2. Over the next week or so, add a few files, delete a few others, and run rsynch maybe a dozen times.
3. Run Verify, and get a "Verify failure: bit mismatch!" error many hours into the Verify process, with a list of files. None of the files in the list have changed recently.

What do I do at this point? Do I have to re-create the RAID from scratch? Is my data still protected?

I should add that I've since run a "Validate" task on the same unchanged configuration, and it reports (4.5 hours later) "Success! The RAID is healthy and up to date!".

So what does it mean when "Verify" fails and "Validate" succeeds?

Hey, is this still an open issue you are having?

Sorry, looks like one of the few questions have not yet answered.

At what bit range and file set does "verify" fails?

Hi Brahim,

I was never able to resolve this issue as I recall, but I've since uninstalled FlexRAID and written my own utility (disParity), so I can't provide any further details about it now.

Thanks!

ObjetDart wrote:Hi Brahim,

I was never able to resolve this issue as I recall, but I've since uninstalled FlexRAID and written my own utility (disParity), so I can't provide any further details about it now.

Thanks!

Cool, thanks.

I did check out disParity.
Good work.

FYI, I ran into a few issues with file edits.
Doing an "update" would crash on me due to the edits.
I meant to file a bug report, but I got sidetracked with other things.

Brahim,

I'd sure appreciate any details you could provide about that crash! Either here or in the disParity forums. I haven't received any other reports of a problem with edits so I have nothing to go on. Do you still have the log.txt available?

ObjetDart wrote:Brahim,

I'd sure appreciate any details you could provide about that crash! Either here or in the disParity forums. I haven't received any other reports of a problem with edits so I have nothing to go on. Do you still have the log.txt available?

Attached are my config and log files.

So, I created a snapshot, did an update, edited a text file, tried an update, and that's when it would simply crash every time.

Thanks Brahim. The only thing I can think of is that while removing the old version of the file from parity, it is encountering an error while trying to access one of the other files from one of the other data paths.

I'll have a new version out soon that will trap the error and log all of the details.