After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 573533 - Rescanning stops early - too fast machine - too slow network?
Rescanning stops early - too fast machine - too slow network?
Status: RESOLVED DUPLICATE of bug 568962
Product: banshee
Classification: Other
Component: Importing
1.4.2
Other All
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-02-28 12:46 UTC by Henrik Enblom
Modified: 2009-06-02 22:42 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Henrik Enblom 2009-02-28 12:46:16 UTC
Please describe the problem:
I got my music stored on a WD MyWorldBook NAS, last week I upgraded my desktop to a AMD Phenom 9350 and 8GB RAM, in short, the machine is lots faster then it used to be. Desktop only have a 10 mbit connection to router (shortage in cable, yes I will replace it soon :) ) I *THINK* this causes banshee to sometimes believe it have finished scanning after only ~200 files when I tell it to rescan, as the writing to the database can be done faster then getting info of the files.

Steps to reproduce:
1. Rescan music library
2. 
3. 


Actual results:
Sometimes the scan stops after ~200 files (there are ~6400 files)

Expected results:
all files should be scanned

Does this happen every time?
no, thank god

Other information:
If I'm correct this should be reproducible with any fast enough machine and slow enough storage media.

I'd be happy with a "wait X seconds before start writing to DB" option hidden somewhere.

This report *MAY* be a duplicate of Bug 561822 & Bug 568962
Comment 1 Gabriel Burt 2009-06-02 22:42:31 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 568962 ***