1/ Adding full drives to a new pool and 2/ snapraid vs file corruption

[iomgui]

1/ Adding a full drive to a new pool.
I ve seen the official guide (requiring stoping services, then fixing the drivepool UI with reset and so on).
But, as long as i disable all balancing plugin, can i not simply move the files directly in the hidden folder and after that reanable the balancing plugin i want to use (assuming here i intend to fill disk by disk and not rebalance between disk, for the simple reason i do not want something in a specific folder to be split between different drives) ?

2/ snaparaid : is it concerned by the fileid problem that could lead to potential file corruption, as long as no application like onedrive or filesyncing app is not use?

[Christopher (Drashna)]

The reset is mostly to ensure that remeasuring occurs.  Triggering just the remeasuring should be fine, though.

And the service stop is to prevent it from running balancing or duplication tasks, and to prevent it from remeasuring while moving data into the pool folder structure.   Eg, we want to make sure it's as un-interrupted as possible.

So, no, you still want to stop the service, as there are other tasks that can be triggered that you don't have as much control over. And since all of these tasks are controlled by the service......

 

> 2/ snaparaid : is it concerned by the fileid problem that could lead to potential file corruption, as long as no application like onedrive or filesyncing app is not use?

The biggest issue is that many apps incorrectly expect that File IDs never change. Which is NOT what the NTFS specifications state.  File IDs can and do change, and if you need the ID to never change, Object IDs should be used.    And the misunderstand and misuse of these behaviors has caused issues.

SnapRAID in no way deals with this problem, as you should be targeting the underlying disks, and NOT the pool.