I wrote this whole thing and then re-wrote it and such, but I decided to check every active NTFS db and they all have a stat page filled.
2 out of 4 folder-only lack a stat page.
I don't get why some do and some don't.
I suppose I can send the original writing in a reply if there isn't a known reason why this may be and it is the solution for me too.
Folder-monitoring only db lack stat page
Re: Folder-monitoring only db lack stat page
So, if I understand correctly ...
- The stats you are referring to are accessible through Menu => Tools => Debug => Statistics
- Here are 2 NTFS Index entries shown (one per drive/volume)
- There are 4 NTFS volumes shown under NTFS options ( Menu => Tools => Options => Indexes => NTFS )
If so:
- Go to Menu => Tools => Options => Indexes => NTFS
- Select the first volume in the Local NTFS Volumes list
- Check if Include in database is enabled
- Select next volume in the Local NTFS Volumes list
- Check if Include in database is enabled
- Repeat for remaining 2 listed volumes/drives.
Are all 4 volumes included in the database?
- The stats you are referring to are accessible through Menu => Tools => Debug => Statistics
- Here are 2 NTFS Index entries shown (one per drive/volume)
- There are 4 NTFS volumes shown under NTFS options ( Menu => Tools => Options => Indexes => NTFS )
If so:
- Go to Menu => Tools => Options => Indexes => NTFS
- Select the first volume in the Local NTFS Volumes list
- Check if Include in database is enabled
- Select next volume in the Local NTFS Volumes list
- Check if Include in database is enabled
- Repeat for remaining 2 listed volumes/drives.
Are all 4 volumes included in the database?
Re: Folder-monitoring only db lack stat page
Please check if the folders are excluded under Tools -> Options -> Exclude.
-
- Posts: 71
- Joined: Tue Oct 08, 2019 6:42 am
Re: Folder-monitoring only db lack stat page
I may have completely forgotten to check this..
But no, each db is separate.
I have 4 folder-only dbs, as in the dbs only monitor when they are on.
2 of those have a stat page as you'd expect, but 2 do not. Those 2's page are completely blank.
Out of the two blank ones, one of them has no exclusions active while the other has maybe 50.
So I presume it's not that.
I was hoping you had come across this and knew of a simple repair mechanic, as restarting the dbs did nothing, removing the db and letting it rescan.
To clarify, by db I mean one separate instance. I have one for each device and then a few folder-only ones that monitor across devices. Like one is for video games to monitor changes or additions to files in the game folders and appdata for their save folders as most go into appdata rather than the game folder you start the game in.
Because I extract/install games on a separate device so if game reading/writing breaks the device, it's not a loss as it's just files I can re-extract/install again, I made a db that works across devices so I can search for all related things for a particular game. There are 3 others that operate like this, because folder-only doesn't cause re-scans it works well across devices where one device may have re-scanned because something went wrong. I don't want to lose index journal, so while they are limited in what they monitor I at least don't lose index journal entries if the NTFS-only db version of whichever device failed re-scans and undoes the index journal.
Maybe when, or if, index journal isn't reset on re-scans will I try NTFS across devices..But then exclusions, big enough, cause a lot of RAM on filename sorting..Or maybe I am thinking of when there are a lot of files and exclusions do not cause significant increase in RAM during sorting stage, either way I don't wan random re-sortings. It can cause max memory and break something without me being aware. So folder-only would still be safer.
I can also point out this isn't a necessary fix, I don't actually use the stat page..But it's still a bug, I presume. If I have it, maybe others do too..Not that any of us have any use for the stat page. I've only used it to check rebuild reason and that doesn't happen with folder-only instances anyway. It's a nice-to-fix, not in any way necessary for any purpose.
But no, each db is separate.
I have 4 folder-only dbs, as in the dbs only monitor when they are on.
2 of those have a stat page as you'd expect, but 2 do not. Those 2's page are completely blank.
Out of the two blank ones, one of them has no exclusions active while the other has maybe 50.
So I presume it's not that.
I was hoping you had come across this and knew of a simple repair mechanic, as restarting the dbs did nothing, removing the db and letting it rescan.
To clarify, by db I mean one separate instance. I have one for each device and then a few folder-only ones that monitor across devices. Like one is for video games to monitor changes or additions to files in the game folders and appdata for their save folders as most go into appdata rather than the game folder you start the game in.
Because I extract/install games on a separate device so if game reading/writing breaks the device, it's not a loss as it's just files I can re-extract/install again, I made a db that works across devices so I can search for all related things for a particular game. There are 3 others that operate like this, because folder-only doesn't cause re-scans it works well across devices where one device may have re-scanned because something went wrong. I don't want to lose index journal, so while they are limited in what they monitor I at least don't lose index journal entries if the NTFS-only db version of whichever device failed re-scans and undoes the index journal.
Maybe when, or if, index journal isn't reset on re-scans will I try NTFS across devices..But then exclusions, big enough, cause a lot of RAM on filename sorting..Or maybe I am thinking of when there are a lot of files and exclusions do not cause significant increase in RAM during sorting stage, either way I don't wan random re-sortings. It can cause max memory and break something without me being aware. So folder-only would still be safer.
I can also point out this isn't a necessary fix, I don't actually use the stat page..But it's still a bug, I presume. If I have it, maybe others do too..Not that any of us have any use for the stat page. I've only used it to check rebuild reason and that doesn't happen with folder-only instances anyway. It's a nice-to-fix, not in any way necessary for any purpose.
-
- Posts: 71
- Joined: Tue Oct 08, 2019 6:42 am
Re: Folder-monitoring only db lack stat page
I was arsed to make a less revealing image, if you read this post before these edits
Here is what I mean by separate dbs, just so there is no confusion..
Each db runs one device in NTFS monitor OR monitors folders without NTFS indexing so unless you re-scan it will only index whenever the folder-only db is on.
https://imgur.com/a/1UdXA8H
And because I thought it may be necessary to show what I actually mean by blank, here is a comparison.
Both only monitors folders, the left one has folder exclusions while the right does not. For the other two, they don't have folder exclusions but one stat page works and one is blank just like these two.
I don't think it's the devices they touch, at least that are active, as they touch the same devices. The left working stat page one touches more active devices.
https://imgur.com/a/ZdYH7zF
Also 3 out of the 4 have extra properties indexed, like date changed and date indexed.
I'd think that's already included in the db but hidden, anyway 2 out of those 3 have blank pages.
So not sure it's extra properties either. 2 of them have the same amount of properties indexed with one having a blank stat page.
Not sure what difference I have that has caused this..
One thing I can think of is that it would be fixed with a system restart which I won't do because this system or/and hardware is broken and automatic repair thing causes issues and I don't know how I get past it so I have no guarantee I can restart and get back in again so I haven't.
It's possible this is related.
I don't know as I don't remember checking these stat pages before the system started with the automatic repair thing on system start, don't know if they were ever filled.
I did get components for a whole new computer which I will eventually build so I can use this old one for testing old components without risking a working computer..
So if this is a new issue and you don't know how to fix it, maybe what I need is just a fresh Windows which I will be doing because of the starting issue that I don't know how I caused..Maybe it's just the SSD, the same model SSD I used for a previous Windows install died after 3 months..This one has lasted 2 years I think.
But just like how long it took to reply, it will probably take 15-30 days to reply after I have set that computer up because of preparations I haven't finalised.
Re: Folder-monitoring only db lack stat page
The statistics text might be too large.2 of those have a stat page as you'd expect, but 2 do not. Those 2's page are completely blank.
There's a text limit of 524288 characters. (I'll up this limit in 1384a+)
The database might not be loaded yet.
If the database hasn't loaded the statistics page will appear blank.
Please try performing a search to make sure your database has loaded.
Close and reopen your statistics page.
If you hover over the statistics window do you see a text cursor?
-This might help indicate an issue with creating the edit box.
edit: this has to be an issue with creating the edit box.
The scroll bars are missing.
Is the text shown if you resize the window?
-
- Posts: 71
- Joined: Tue Oct 08, 2019 6:42 am
Re: Folder-monitoring only db lack stat page
One db is only 62,000 characters and that has a bunch of folders monitored, not sure how many more characters I could really get out of one db..
The database is definitely loaded, I use it to make archives of files across devices from time to time.The database might not be loaded yet.
If the database hasn't loaded the statistics page will appear blank.
Please try performing a search to make sure your database has loaded.
Close and reopen your statistics page.
Index journal and main db runs fine.
If you mean the desktop cursor, it is there yes. Just a blank page.If you hover over the statistics window do you see a text cursor?
-This might help indicate an issue with creating the edit box.
Just to test I just now ctrl+a and ctrl+c and nothing came of it.
Here is what it looks like full screen, it didn't act any different re-sizing it smaller and bigger so just made a screenshot of when it's biggest to show stuff in as much detail.edit: this has to be an issue with creating the edit box.
The scroll bars are missing.
Is the text shown if you resize the window?
Re: Folder-monitoring only db lack stat page
Thanks for the screenshot.
The edit window is created, it's a rendering issue.
Too many GDI objects maybe?
In the Task Manager (Ctrl + Shift + ESC)
Click the Details tab.
Show the GDI Objects column (View -> Select columns)
How many GDI Objects is Everything using?
Are there any processes with over 1000?
The cap is around 10000 per process (and there's a global limit of 65536).
Once you hit the cap you will start seeing artifacts like in your screenshot.
The edit window is created, it's a rendering issue.
Too many GDI objects maybe?
In the Task Manager (Ctrl + Shift + ESC)
Click the Details tab.
Show the GDI Objects column (View -> Select columns)
How many GDI Objects is Everything using?
Are there any processes with over 1000?
The cap is around 10000 per process (and there's a global limit of 65536).
Once you hit the cap you will start seeing artifacts like in your screenshot.
-
- Posts: 71
- Joined: Tue Oct 08, 2019 6:42 am
Re: Folder-monitoring only db lack stat page
No EBV process goes above 500, VGS itself is 72-82. That's the db in the screenshot.void wrote: ↑Fri Nov 22, 2024 3:36 am Thanks for the screenshot.
The edit window is created, it's a rendering issue.
Too many GDI objects maybe?
In the Task Manager (Ctrl + Shift + ESC)
Click the Details tab.
Show the GDI Objects column (View -> Select columns)
How many GDI Objects is Everything using?
Are there any processes with over 1000?
The cap is around 10000 per process (and there's a global limit of 65536).
Once you hit the cap you will start seeing artifacts like in your screenshot.
Re: Folder-monitoring only db lack stat page
Thanks for the GDI object information.
Nothing sounds out of the ordinary here..
Is it just the stat page causing the trouble?
Does Help -> Search Syntax work correctly?
Both the stat page and search syntax use the same "help" code.
Nothing sounds out of the ordinary here..
Is it just the stat page causing the trouble?
Does Help -> Search Syntax work correctly?
Both the stat page and search syntax use the same "help" code.