Drive Access (possible Video Archive Issue)

[renzema]

Hi All (and Jeff),

I have upgraded to the latest GBPVR and Video Archive Plugin. Since I have done this upgrade, the external NAS disks never spin down.

I have disabled the VA plugin, but this does not appear to have fixed the situation. (I initally thought that it was VA scanning the drives).

It appears that every 10 minutes, GBPVR is scanning all of the files in its database. I think that with the latest release of VA, the file locations in GBPVR are now updated (When files are archived, the GBPVR database is updated with the new file location so that other recordings plug-ins should continue to work even though the file has been moved.) and this is causing the issue.

Using the SysInternal File Monitor, this is what I see every 10 minutes.

[SIZE="1"]10:41:56 AM GBPVR.exe:2560 CLOSE G:\Video Archive\Harry Potter och hemligheternas kammare\ SUCCESS
10:41:56 AM GBPVR.exe:2560 OPEN G:\Video Archive\Harry Potter och hemligheternas kammare\ SUCCESS Options: Open Directory Access: All
10:41:56 AM GBPVR.exe:2560 DIRECTORY G:\Video Archive\Harry Potter och hemligheternas kammare\ NO SUCH FILE FileBothDirectoryInformation: *.gif
10:41:56 AM GBPVR.exe:2560 CLOSE G:\Video Archive\Harry Potter och hemligheternas kammare\ SUCCESS
10:41:56 AM GBPVR.exe:2560 OPEN G:\Video Archive\Harry Potter och hemligheternas kammare\ SUCCESS Options: Open Directory Access: All
10:41:56 AM GBPVR.exe:2560 DIRECTORY G:\Video Archive\Harry Potter och hemligheternas kammare\ NO SUCH FILE FileBothDirectoryInformation: *.lnk
10:41:56 AM GBPVR.exe:2560 CLOSE G:\Video Archive\Harry Potter och hemligheternas kammare\ SUCCESS
10:41:56 AM GBPVR.exe:2560 OPEN G:\Video Archive\Harry Potter och hemligheternas kammare\ SUCCESS Options: Open Directory Access: All
10:41:56 AM GBPVR.exe:2560 DIRECTORY G:\Video Archive\Harry Potter och hemligheternas kammare\ NO SUCH FILE FileBothDirectoryInformation: *.iso
10:41:56 AM GBPVR.exe:2560 CLOSE G:\Video Archive\Harry Potter och hemligheternas kammare\ SUCCESS
10:41:56 AM GBPVR.exe:2560 OPEN G:\Video Archive\Vita huset\ SUCCESS Options: Open Directory Access: All
10:41:56 AM GBPVR.exe:2560 DIRECTORY G:\Video Archive\Vita huset\ NO SUCH FILE FileBothDirectoryInformation: *.mpg
10:41:56 AM GBPVR.exe:2560 READ G:\Video Archive\Vita huset\ SUCCESS Offset: 0 Length: 8192
10:41:56 AM GBPVR.exe:2560 CLOSE G:\Video Archive\Vita huset\ SUCCESS
10:41:56 AM GBPVR.exe:2560 OPEN G:\Video Archive\Vita huset\ SUCCESS Options: Open Directory Access: All
10:41:56 AM GBPVR.exe:2560 DIRECTORY G:\Video Archive\Vita huset\ NO SUCH FILE FileBothDirectoryInformation: *.mpeg
10:41:56 AM GBPVR.exe:2560 CLOSE G:\Video Archive\Vita huset\ SUCCESS
10:41:56 AM GBPVR.exe:2560 OPEN G:\Video Archive\Vita huset\ SUCCESS Options: Open Directory Access: All
10:41:56 AM GBPVR.exe:2560 DIRECTORY G:\Video Archive\Vita huset\ NO SUCH FILE FileBothDirectoryInformation: *.avi
10:41:56 AM GBPVR.exe:2560 CLOSE G:\Video Archive\Vita huset\ SUCCESS [/SIZE]

This repeats for every directory that I have on two drives (G + H). Surprisingly, it does not occur for the K Drive, which is also defined as an archive, nor for the F Drive, which is my primary storage.

I am at a loss to explain why this is occuring. Can anyone shed light on this problem?

Thanks,

Josh

[Jeff]

You are right, that is kind of what it is doing. When it can, the plug-in uses the FileSystemWatcher class to monitor drives for files that are added, moved, or deleted. When it sees one of these events it automatically updates its list. On NAS drives (I have one too) these events are not fired by Windows, so, for these drives I build a list of the video files on the disk and scan the disk at an interval to see if the files are still there and if new ones have been added. The default interval to check is every 10 minutes. You can change this by creating a property in the Video Archiver property of the config.xml file called NetworkDriveMonitorInterval and setting it to the number of minutes you would like between intervals. Also, the way I check to see if Windows disk monitoring works is to create a junk file and see if a file create event is fired. This means that I will incorrectly detect native Windows read-only drives as NAS drives and monitor them manually. If someone knows a more efficient way to monitor NAS drives I would appreciate the tip.

Jeff