Ok my experience with .40 thus far
Set to notify of changes, working as expected
Set to update after 1 minute of inactivity, working as expected
Changed the files on the drive when update in progress, it saw the changes and ran another update after 1 minute of inactivityMade no changes to the drive but browsed to a directory and got properties of a file, disParity saw this as a change and re-scanned that drive after 1 minute (could this be due to drive bender I wonder or is getting file properties an actual change to the drive), at any rate it scanned and found no changes.
I will post anything else I find as I continue to try and break it :)
Ed
Edit: So it seems that even accessing a file on my drive is detected as a change and disParity will rescan that drive. I will do more testing and see if this is related to how windows access data or if maybe Drive Bender is writing files to the drive when I access things. I do have DP set to ignore *.$DRIVEBENDER files as those do change frequently
Edit Again: This appears to only happen when I access files via my Drive Bender pool, if I share the individual drives directly and perform the same tests DP does not see any changes to the drive. I played a movie and got properties on it from both my computer via network share and directly from the server itself using both the individual drive and then the same file from the pool. This only happens on the pool so I will look into DB and see what's going on there.
____________
So it would appear that most of these drive changes are definitely related to Drive Bender. I'm not sure how to get around this issue other than to set the scan time to a higher number to reduce the number of scans being performed. If I find a solution, I'll post back for anyone else using DB with disParity
________On a brighter note .40 seems to be working smashingly :)
Thanks Roland for all your hard work
Ok so did some more testing today....
A) Attempted to move a file while DP was scheduled to update that specific file, it would not allow move but it would copy it. I'm glad to see this in case someone on my network goes moving things around while DP is updating.
B) Still no solution to the Drive Bender problem. It's not detrimental but it does cause excess scans
C) Renaming a file will cause DP to scan the drive and update parity regardless if it is in scan mode or update mode (Is this expected behaviour?) for instance if I rename a file and click scan all DP will recognize this change and fix it even though I didn't tell it to update
D) Renaming a file and then moving it to another location on the same drive will show the same results as "C" above
E) Renaming and moving a file in a single operation (using a program like filebot) shows as 1 file deleted and 1 file added
F) Renaming a file with filebot and leaving it in place also has the same effect as "E" above
Judging by what I can tell, filebot uses a read/write operation from on file to another and then removes the original file (not sure about this but it appears so) so I would guess this is expected behaviour from disParity. Although is is very disappointing on filebot's behalf since it takes substantially longer to update parity because of this.
The only possible problem I see is "C" and "D" above, as this is during a scan process and I would not expect DP to make any changes, only to report them.
Roland,
Sorry for mentioning all these other programs. If it bothers you I will not do it. I just feel it's important to document DP's interaction with the other programs that will most likely be used by people.
Ed