Rockbox General > Rockbox General Discussion

overactive dir cache?

<< < (2/4) > >>

squidkidd:
Another "symptom" I noticed was that I tried to disable the dircache and then re-enable it.  it prompted me to reboot, and when I did that, it did *not* scan the disk.  I checked in debug to see if the cache was working and it was not.  I had to restart I think twice more before it would scan and enable dircache again.  I even tried a reset in there before it would scan.

Brian

bascule:
Well, I'm stumped.

My Gigabeat very occasionally seems to scan for no apparent reason on startup, but I live with it.

I *guess* that whatever checks to see if there have been any disk changes, which I *presume* is done by scanning the File Allocation Table on startup just sometimes bugs out...  :-\

As you can tell, I'm no expert in this matter.

squidkidd:
Ok, this just keeps getting more and more frustrating.  I have now discovered that whenever my player starts and does not scan the disk, dircache is not enabled (I checked through the debug info).  So the only time dircache gets enabled to start with is every other time it starts and says scanning disk.  Does this shed light on anything?

Brian

squidkidd:
I think I might be a little confused as to how dircache actually works.  I have now discovered that those times when the disk does not scan on startup, and I check in debug, and it says dircache is not initialized, if I give it long enough (601sec for instance) it will eventually say dircache initialized.  Does this mean dircache scans disk every time the player is turned on, it just does it though in the background?  I thought dircache disk scanning was a rare thing, and that the whole point of it was to save on disk spinning.

way confused,
Brian

Llorean:
Considering the iPod has several modes you can get to without any Rockbox code every running, how is Rockbox supposed to know what you did between last time you ran it and this time?

Dircache *has* to check to see if files have changed. On some players there is no mode that doesn't go through some of our code first. On those we can prevent Dircache from needing to check.

Dircache prevents additional spinups and spindowns while browsing. For people who browse the filetree often it means many, many less disk spinups (specifically: One when you boot, plus any time the buffer needs refilled or a file needs to actually be loaded such as running a plugin).

Are you saying it took a literal 10 minutes for dircache to scan your drive?

Navigation

[0] Message Index

[#] Next page

[*] Previous page