-
-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Force Scan Still Running (after 24 hours) #3414
Comments
It all depends on how big your library is. You haven't provided any info at all to help us. |
12,933 files, however, it is unclear if that is counting folders too. What took 2-3 hours before is taking more than 24 hours now though. That should be enough information to compare from before update to instructions stating new scan could take longer. This much longer expected? |
As I explained in the release notes, first scan/force scan will take MUCH longer than before. Once this scan is complete, the subsequent scans shouldn't be noticeable and should be much more reliable. |
I am quite ok if it WILL take that long, I was just concerned if this was taking way far beyond anything expected. Thank you for the reply, I will continue to let it scan. Thankfully it is not getting hung up so far, which has happened in the past. |
Would scanning each series individually achieve the same effect a a forced library scan? |
What happened?
Should this be taking that long? It does still appear to be processing, but that's a long time.
What did you expect?
Maybe 3-4 hours but not 24
Kavita Version Number - If you don not see your version number listed, please update Kavita and see if your issue still persists.
0.8.4 - Stable
What operating system is Kavita being hosted from?
Linux
If the issue is being seen on Desktop, what OS are you running where you see the issue?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
No response
If the issue is being seen on Mobile, what OS are you running where you see the issue?
None
If the issue is being seen on the Mobile UI, what browsers are you seeing the problem on?
No response
Relevant log output
No response
Additional Notes
No response
The text was updated successfully, but these errors were encountered: