Idk if I'm blind or never mentioned after my last reply, but adding as folders means it won't know it's offline. Hence why it dims when they're added as NTFS.
The only benefit I've found with folder-monitoring is that it doesn't reach a point where it might want to rebuild the index if you take it offline and online again as it doesn't try to read changes to the device while it was offline or used elsewhere or without an EBV instance for it running.
I use that benefit for larger property-heavy instances.
System crashes can be one of those instances where it will want to rebuild the index..Or at least system crashes that happen after enough changes without saving the db has occurred. For me that's only or almost only the OS device itself due to how many reads and writes take place in a day. So the 2 instances that touch the OS device will usually have to be rebuilt after system crashes.
I believe with NTFS it doesn't read the journal if the instance is on when you plug it in again.
Not that I remember if I ever checked this, but I always exit any instance touching a device before plugging it in again so any possible changes will be read again. This doesn't matter much if either the instance only takes some seconds to rebuild or you don't care about the journal. I try to separate dbs after the journals reach near max capacity.
Either the journal reading is separate from reading file changes or they do both occur while the instances touching those devices were never closed. As in keeping an instance on without the device it touches being plugged in and adding or changing files on that device with say a different computer and then plugging it in again..It will find those new/modified files but not have any new entries in the journal section. I will probably never do such a test and I don't know the answer. Unless I can do a quick one with one of the NTFS USB-sticks I have..Eh.
The only benefit I've found with folder-monitoring is that it doesn't reach a point where it might want to rebuild the index if you take it offline and online again as it doesn't try to read changes to the device while it was offline or used elsewhere or without an EBV instance for it running.
I use that benefit for larger property-heavy instances.
System crashes can be one of those instances where it will want to rebuild the index..Or at least system crashes that happen after enough changes without saving the db has occurred. For me that's only or almost only the OS device itself due to how many reads and writes take place in a day. So the 2 instances that touch the OS device will usually have to be rebuilt after system crashes.
I believe with NTFS it doesn't read the journal if the instance is on when you plug it in again.
Not that I remember if I ever checked this, but I always exit any instance touching a device before plugging it in again so any possible changes will be read again. This doesn't matter much if either the instance only takes some seconds to rebuild or you don't care about the journal. I try to separate dbs after the journals reach near max capacity.
Either the journal reading is separate from reading file changes or they do both occur while the instances touching those devices were never closed. As in keeping an instance on without the device it touches being plugged in and adding or changing files on that device with say a different computer and then plugging it in again..It will find those new/modified files but not have any new entries in the journal section. I will probably never do such a test and I don't know the answer. Unless I can do a quick one with one of the NTFS USB-sticks I have..Eh.
Statistics: Posted by Herkules97 — Sat Jun 20, 2026 1:17 pm
