bigbirdtrucker

My pool size is 54tb with freespace of 18tb (all drives contain data) I'm going to enable duplication for one copy of each drive once I add enough new drives to cover the space needed for that (in my case an additional 36TB, correct?) I read on the forum of someone who moved their data from the original location to the hidden Poolpart folder (on that same drive) (called seeding) in order to see the files already in the pool. Do you recommend doing this? Should I be copying or moving my files into the pooled drive? If I do move my files to the hidden Poolpart directory from the same drive... are there risks if I then remove the drive later? Such as would the files then be erased form disk if I move the files to the poolpart folder on the same drive - for each drive with the intention of seeing the files in the pool? When I add drives to the pool that contain data I rad that stablebit drivepool doesnt modify those files. Am I correct to assume that even without moving the files to the poolpart folder from the same drive that the files that are on the drive at the time of creating the pool are indeed already in the pool (yet not visible)? Is it true that when duplication is enabled that drivepool will place my files across several of my drives which have ample space? While I understand the benefits of leaving my files in place on the origin drive....those files are automatically part of the pool when added right? Even though it took literally zero time to add them to the pool with over 30tb on the drives combined? How will I know which files are on which drive when it comes time to recover from a lost disk for instance? Is there a reason that the pooled drive appears empty when drives with data are added to it? Do I need to have my files visible on the pool (i.e. moving the files to the poolpart dir on the same drive for each drive in order to let snapraid see my pool and protect it with parity?