So DPCMD on the POP will show two devices which are in fact Pool1 and Pool2? Not the actualy underlying physical devices?
Yes. I believe that is the case, I haven't had a chance to really play around with this, but based on how I know the software works... this should be the case. (basically, it treats the pools like any other, normal disk)
I have just upgraded to 746. Changed the $recycle.bin to 1 x dup and checked the pool and folder duplication was still 2x for everything else. Also, the task failed error has gone as per the 746 change log. I am doing some logging at the moment so will post it through it I see any odd behavior.
Edit: Actually, something I am seeing a lot is that the real time duplication doesn't seem to work. This may sound more drastic than it actually is. I am seeing large files copied or moved or overwritten in the pool and then the master pool will say, as an example 8.81GB is not duplicated, so it kicks off a duplication run, when it is finished I have 5xMB unduplicated. I am wondering it the <random file names>.copytemp from pool A and Pool B are being picked up when and if those pools balance themselves and if a balance in Pool A or Pool B will affect the Duplication in the Master Pool. I will post some logs when I have the time to work on this.
Edit 2: Logs uploaded for continual duplication runs.
If your'e able to reproduce this, could you run the "dpcmd X:\$RECYCLE.BIN", where "X:" is the top level pool. both before and after, to verify the duplication level.
Ignore the list of folders, and look at the "expected number of copies" value.
If you can reproduce this, then enable file system logging, reproduce and then turn off logging. Upload the logs,
As for the real time duplication, I'll see about reproducing this later.
But could you use the "dpcmd list-pool-fileparts" command on the specific file, to verify if it's at both locations?
If that's having issues, then please do the above (enable logging, reproduce the issue, turn off logging and upload the logs).
As for "copytemp", this is what we use for balancing and duplication. This way, if something happens (bSOD, crash, sudden power loss, etc), that there isn't a partial file on the destination, leaving you with a corrupted file. So if you're seeing this, it means "it's doing something".