Copying PoolPart folder???

[xazz]

Is it OK to do this:

 

1. Turn off PC

2. Remove a 1TB HDD

3. Copy the PoolPart folder from the 1TB to a new 6TB HDD

4. Insert the 6TB HDD to PC

5. Turn on PC and Remeasure in DrivePook

6. Use the 1TB HDD to stabilize an uneven table

 

Thanks

[Christopher (Drashna)]

Depends on what you're trying to do.

 

The approved method would 

1. Add 6TB drive to pool
2. Remove 1TB drive from pool
3. Remove 1TB from system.

or 

1. Remove 1TB drive from pool
2. Add 6TB drive to pool

(and at some point, remove the 1TB from the system)

 

Otherwise, you shouldn't mess with the Poolpart folders directly, unless there is a VERY, VERY good reason.

 

The software itself will handle moving the data around. No need to do this yourself. Again, unless there is a VERY, VERY specific reason.

 

 

Also, hard drives contain rare earth magnets.  They're super strong, but only over short distances.  All sorts of fun things you can do with them (but be careful, don't get a finger stuck between them)

[xazz]

No, no good reason.

 

It might be useful when removing a drive you could choose not to remove the files it contains (i.e. it would copy the PoolPart content to another drive, and then move it to a non-pool folder of the same drive). That would save be about 23 hours of copying today   But my usage may not be typical...

[Christopher (Drashna)]

Well, if you want to remove the drive and replace it and you don't give a shit about the contents on the drive, you could just pull the drive from the system.  This will cause the disk to go missing ... obviously.  Just remove it in the UI and then add the new drive.  

 

Alternatively, there is the "dpcmd" "ignore-poolpart" command which immediately drops the drive from the pool

Also, if you have duplication enabled, the "duplicate data later" skips the duplicated files that exists on other disks, and leaves them behind.  It then duplicates the files, as needed, once the disk is removed.

 

 

Also, we've reworked the removal code to be faster and more efficient, and .... to keep the pool "online" (not read only) when removing a disk.   So, that may help out here.