v1.4.1.899 - settings always reseted ?!

[Garfield]

Greetings,

I'm not sure if it is a bug, therefore I need your help/advice.

I'm using Stablebit Drivepool and Everything and tried to solve a nasty problem already adressed here: viewtopic.php?t=1572

While editing the INI everything service and front end was stopped, I edited and saved the INI, confirmed my changes and re-starteded the service & front end - a new DB scan showed me my edit wasn't successfull. Therefor I had a look in the UI settings, couldn't recognize any changed based on my manual INI changes, closed the front end and stopped the service again. Now re-opening the INI again and all my manual changes were gone.

To debug my problem I've done several trials - now I can say this: after closing the UI the settings are always written to the INI and manual changes to the ntfs_volume_* part are resseted to UI settings.

Can anyone confirm this OR maybe push me in the right direction, please.

Happy Easter!

[NotNull]

Most likely you are editting the wrong INI file.
If you type

Code: Select all

about:config

in the search bar, it will open the actual Everything.ini that it is using.
You can't make changes here (those will be overwritten), but if you do a Menu:File > Save As , you can find the actual llocation.

This might be caused if you are running Everything as an administrator. That is (almost) never the best way to run Everything.
Change thing back to normal by changing the following settings under Menu:Tools > Options > General :
- Enable Everything Service
- Disable Run as Administrator

[Garfield]

Hi,

thanks, tried both advices with no success:
- my INI path was the correct one, same as in settings "General = default" => %appdata%\everything\everything.ini
- EV is running as service, nevertheless I have resseted my general settings to default

to clarify things up - here are my settings and my system (fresh win10x64 latest fixes, stablebit drive pool, bitdefender, everything 1.4.1.899x64, nothing else), F: + G: are my pool drives, both mapped to I: by drivepool

Starting Point after new install
ntfs_volume_guids="\\\\?\\Volume{000d0054-0000-0000-0000-60e609000000}","\\\\?\\Volume{000d0054-0000-0000-0000-108813000000}","\\\\?\\Volume{cf59c0a1-90c0-4313-a923-93b59098d678}","\\\\?\\Volume{d41e1ccc-e205-4c98-a9c2-be2a51900bb7}","\\\\?\\Volume{fca626da-9722-4547-acdb-d776e2607ad6}","\\\\?\\Volume{185bdf5d-0000-0000-007e-000000000000}","\\\\?\\Volume{d61be005-715b-4f1d-a070-b982061ef1af}"
ntfs_volume_paths="C:","D:","E:","F:","G:","H:","I:"
ntfs_volume_roots="","","","","","",""
ntfs_volume_includes=1,1,1,1,1,1,0
ntfs_volume_load_recent_changes=0,0,0,0,0,0,0
ntfs_volume_include_onlys="","","","","","",""
ntfs_volume_monitors=1,1,1,1,1,1,1

Manual Changes
ntfs_volume_guids="\\\\?\\Volume{000d0054-0000-0000-0000-60e609000000}","\\\\?\\Volume{000d0054-0000-0000-0000-108813000000}","\\\\?\\Volume{cf59c0a1-90c0-4313-a923-93b59098d678}","\\\\?\\Volume{d41e1ccc-e205-4c98-a9c2-be2a51900bb7}","\\\\?\\Volume{fca626da-9722-4547-acdb-d776e2607ad6}","\\\\?\\Volume{185bdf5d-0000-0000-007e-000000000000}","\\\\?\\Volume{d61be005-715b-4f1d-a070-b982061ef1af}"
ntfs_volume_paths="C:","D:","E:","I:","I:","H:","I:"
ntfs_volume_roots="","","","PoolPart.dc96ae0f-1048-4e9d-b606-c90600102400","PoolPart.1812c8d0-9bb8-408d-b5a4-d831c7d9c1bc","",""
ntfs_volume_includes=1,1,1,1,1,1,1
ntfs_volume_load_recent_changes=0,0,0,0,0,0,0
ntfs_volume_include_onlys="","","","","","",""
ntfs_volume_monitors=1,1,1,1,1,1,1

EV settings
ntfs_volume_guids="\\\\?\\Volume{000d0054-0000-0000-0000-60e609000000}","\\\\?\\Volume{000d0054-0000-0000-0000-108813000000}","\\\\?\\Volume{cf59c0a1-90c0-4313-a923-93b59098d678}","\\\\?\\Volume{d41e1ccc-e205-4c98-a9c2-be2a51900bb7}","\\\\?\\Volume{fca626da-9722-4547-acdb-d776e2607ad6}","\\\\?\\Volume{185bdf5d-0000-0000-007e-000000000000}","\\\\?\\Volume{d61be005-715b-4f1d-a070-b982061ef1af}","\\\\?\\Volume{d41e1ccc-e205-4c98-a9c2-be2a51900bb7}","\\\\?\\Volume{fca626da-9722-4547-acdb-d776e2607ad6}"
ntfs_volume_paths="C:","D:","E:","I:","I:","H:","I:","F:","G:"
ntfs_volume_roots="","","","PoolPart.dc96ae0f-1048-4e9d-b606-c90600102400","PoolPart.1812c8d0-9bb8-408d-b5a4-d831c7d9c1bc","","","",""
ntfs_volume_includes=1,1,1,1,1,1,1,1,1
ntfs_volume_load_recent_changes=0,0,0,0,0,0,0,0,0
ntfs_volume_include_onlys="","","","","","","","",""
ntfs_volume_monitors=1,1,1,1,1,1,1,1,1

bye

[NotNull]

Before diving into the drive settings, let's make sure manual changes to the INI are effective:

• Close running Everything: Systemtray > rightclick Everything icon > Exit
• Open %appdata%\Everything\everything.ini in your text editor
• Change this setting: fullscreen=0 to fullscreen=1 (or visa-versa)
• Save the INI file
• Restart Everything.

Is Everything (no longer) fullscreen?

[Garfield]

Good Morning,
I changed INI to fullscreen=1 and EV started as told in fullscreen with no menubar (btw, terrible view)
=> this manual setting is working and not modified by EV

[NotNull]

That's good news.
I interpreted

Therefor I had a look in the UI settings, couldn't recognize any changed based on my manual INI changes, closed the front end and stopped the service again. Now re-opening the INI again and all my manual changes were gone.

as a problem writing to/finding the right INI file, but apparently it's about the drives.

Anyway ... I don't know Stablebit Drivepool, but by the look of the INI, it presents an extra disk with the contents of multiple other disks (i.e. x:\somefolder\somefile + y:\somefolder\anotherfile = z:\somefolder\ somefile AND anotherfile)

Default, Everything will add and remove disks automatic (like plug 'n play). I think that mechanism messes up your disklist.
Try it by disabling this dynamic bhaviour and create a static list of all your disks. Add this to your Everything.ini:

Code: Select all

[everything]
auto_include_fixed_volumes=0
auto_include_removable_volumes=0
auto_remove_offline_ntfs_volumes=0
auto_remove_moved_ntfs_volumes=0

PS.I guess you did a lot of manual editing of your Everything.ini. Maybe this can make that a little easier for you.
Basic idea: save the settings mentioned above to a file, drag/drop that to the Inject.cmd script and you're done. The script will also stop and start Everything for you.

[Garfield]

Hi,

problem solved - Thank you very much

The settings for "fixed" and "offline" did the trick.
Now I'm able to have Drivepool pooling & balancing my JBOD, duplicating my important files and to use EV in conjunction to find files on the virtual Drivepool drive without the Pool Drives in the DB

My NAS setup:
E: = HDD for Drivepool AND (!!) Files not belonging to the Pool
=> here I have to tackle once more with the setting to achive this (if possible):
=> Drivepool Part of E: remapped to virtual Drivepool Drive I: and Non-Pool part shown as E:
F: = HDD for Drivepool => remapped to virtual Drivepool Drive I: and not listed in EV
G: = HDD for Drivepool => remapped to virtual Drivepool Drive I: and not listed in EV
I: = virtual Drivepool Drive

I interpreted

well ... (how to say it in english) ... your interpretation was not totally wrong, but not belonging to the location of the INI or to admin vs service.
I started this threat because I had an issue with my INI in the way that ALL my manual changes were always resseted by EV. This behavier was my wrong interpretation of what really happened, but at this time this was my understanding of what was going on.

Now as you solved my main problem (path remapping) my understanding is like this:
I did the manual INI changes and tried to find them in the UI settings. because there is no equivalent in the UI and my tamperings in the UI led EV to save its settings as shown in the UI. From EV perspective totally correct, from my point of view wrong as it looks for me like a reset of my manual INI changes.
If my understanding is in some way correct an advice from EV would be great if there exists a conflict between manual and UI settings.

[NotNull]

If my understanding is in some way correct an advice from EV would be great if there exists a conflict between manual and UI settings.

I'm not @void (the "author" of Everything) and I didn't understand most of your theory, but I'm fairly certain there is no difference between UI and manual settings. Though there are some settings you can only make manually in the INI file

... (how to say it in english) ...

Dutch by any chance?

[Garfield]

Dutch by any chance?

German, with known problems in tenses and grammar and much too less possibilities to speak with nativ speakers ...

[NotNull]

Dutch by any chance?

German

That's more of the same, language structure-wise . I thought I recognized some patterns .. (I'm Dutch, btw).

E: = HDD for Drivepool AND (!!) Files not belonging to the Pool
=> here I have to tackle once more with the setting to achive this (if possible):
=> Drivepool Part of E: remapped to virtual Drivepool Drive I: and Non-Pool part shown as E:
I: = virtual Drivepool Drive

That sounded really complicated. And thus a nice challenge ...
But as it turns out, this is completely straightforward! (Good for you, but not for me )

I have no complicated disk-setup (just 1 disk, C:), so this was a simulation where the C:\Tools folder was presented as I: and c:\Tools was no longer included in the Everything result list.
These were the settings I had to make in the INI to make it work:

Code: Select all

;"diskC","diskI"
ntfs_volume_guids="\\\\?\\Volume{ddd1ecb4-0000-0000-0000-f01500000000}","\\\\?\\Volume{ddd1ecb4-0000-0000-0000-f01500000000}"
ntfs_volume_paths="C:","I:"
ntfs_volume_roots="","Tools"
ntfs_volume_includes=1,1
ntfs_volume_include_onlys="",""
ntfs_volume_monitors=1,1
auto_include_fixed_volumes=0
auto_include_removable_volumes=0
auto_remove_offline_ntfs_volumes=0
auto_remove_moved_ntfs_volumes=0
exclude_folders="C:\\Tools"

[Garfield]

Hi,
so as Easter is over back to business ...

I compiled your settings to my NAS setup and it is working great except for multiple identical file names (for DrivePool this means auto-duplicated files).
This means:
- OK: all folder shared across multiple disks are reported as one folder
- OK: disks which are belonging to the pool AND have shared files NOT belonging to the pool are reported correct
- False: identical file names are now reported n times with the remapped path (a new way of duplicated file names finder )
=> this is a feature of DrivePool and could also easily be solved by changing the settings for "Duplication Disk" to a known one and excluding the known duplication path in EV, but would lever the feature a bit

For me and my setup this is acceptable as my main problem is still solved (reporting with DrivePool virtual Drive).
As for the long future - I'm planning to experiment with BTRFS and rsync for a new DIY NAS ...

Thanks again for your expert support !


PS:
should the Threat title be changed as this is more a threat for EV + DrivePool and who can to the change?

[NotNull]

Hi,
As for the long future - I'm planning to experiment with BTRFS and rsync for a new DIY NAS ...

I'm a fan of BTRFS for years! Core filesystem is stable; tooling etc. is still a little behind (last time I checked, about a year ago). Using rsync for synchronization is maybe for now the best option, but that ignores all the powers and possibilities of BTRFS. There shouls be better solutions around (BTRFS specific) ...

Thanks again for your expert support !

You made me laugh out loud when reading this! I have no experience with DrivePool, nor had I with these INI settings. So I don't consider myself an expert. But thanks for the compliment and ... gern gemacht!

should the Threat title be changed as this is more a threat for EV + DrivePool and who can to the change?

You can change the title by editing the opening post of this thread. The subject -all the way on top - is editable.