andyg;432962 Wrote: > Yikes. Are G: and E: both on the same drive/share? I don't think my > changes today would cause this. Was it much faster before?
It's OK now. I killed the server and the scanner process, wiped out everything in the cache, including the database files and restarted the server. It rescanned the library and only took only 1:06 to scan 1100 files. In the scanner log the first time I saw a couple errors, complete with tracebacks, regarding database file locks. Maybe that was what it was dealing with. Could the 10 seconds have been some kind of timeout? The second scan showed no errors. The other thing I noticed during the first scan was that there was no progress being reported at all on the web info page under scan details. One of the downsides to wiping out the scanner log for every scan is that you can't go back and compare details from successive scans, or see old errors. If you want fresh logs, it might be better to rotate them and keep a few of the old ones. -- JJZolx Jim ------------------------------------------------------------------------ JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=64567 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
