Silenus

Further information: In the MS Word doc's case, I tracked down the two duplicated files from the pool's underlying drive. One was a 2-page 158kb file from before a big edit, and the other one was a 5-page 670kb file from after a big edit, so it aligns with my hypothesis above. Another data point, is that MS Word seems to be aware of the pool parts!!! This is what I see when I click "Save As": I've spoken with my wife whose file this is, and she tells me the trouble started after the computer was restarted without Word properly shutting down. When it re-opened it asked if it should recover the file. She said yes, and then used Save As to save it. Maybe the auto-recover tool somehow operates directly against the underlying file by doing some kind of file-system magic for recovery?

Hi again, I'd like to get some further advice on this. Forget the Oculus stuff, I think that's a red herring which derailed the discussion. I've now had three cases of files corrupting themselves without me doing any7 "under the hood" touching of files. 1) The case above, with the Lone Echo save game (Lone Echo the game, not Oculus Home the store) 2) A Word document created on the pool 3) A JPG image imported from my phone via Lightroom In all cases, I get the duplication mismatch error (screenshot attached). If I can't get to this root cause of this, I'm going to have to (reluctantly) give up on Drive Pool and find a different solution. I can't have files randomly corrupting themselves from basic read/write operations. The one common thing between all of these: they are all impacted by some kind of placement rule. The save game was part of a folder pinned to SSD, the word doc is in a folder that is duplicated, as is the JPG. I've also attached a screenshot of which plugins I have enabled. My software developer intuition is telling me what is happening is this: the file is rebalanced while a program still has it open; somehow the program has a pointer to the original location and keeps writing there, while DrivePool has rebalanced the other copy somewhere else. As a result there are two copies with different content. Is this possible? I should hope not as the userspace programs should never know where the file truly is, but I don't know.

Thanks guys. I didn't realize it was okay to install stuff to the pool part folder. I figured that was a recipe for disaster. If I do that, will DrivePool eventually try to rebalance it?

After some further investigation, I've found that Oculus Home is simply unable to install games onto the pool, or update existing games that I've manually moved to the pool. This is likely unrelated to the Lone Echo problem, as the game doesn't rely on Oculus runtime for file access, but it might be something to add to the known issues list. Could this be related to hard links, like the Plex problem?

I have a pool with with a bunch of large HDDs and two SSDs fronting as the write buffer using the SSD Optimizer. On this pool, I have the Oculus Rift game Lone Echo. As I'm not actively playing it much, it's sitting on Archive disks (as in, I have no special placement rules forcing it onto one of the SSDs). A friend has been playing lately, and has had several crashes. After looking into the crash dump of the game, I found this: Encountered an error: - 0x2FD48A8D4C79448D - 0x2FDA8A8C4D75508F: While operating on file 'Could not move e:\games\oculus\software\ready-at-dawn-lone-echo\_local\saves\slot3\prevautosave1.radsave to e:\games\oculus\software\ready-at-dawn-lone-echo\_local\saves\slot3\prevauto Encountered an error: - 0x2FD48A8D4C79448D - 0x2FDA8A8C4D75508F: While operating on file 'Could not move e:\games\oculus\software\ready-at-dawn-lone-echo\_local\saves\slot3\autosave.radsave to e:\games\oculus\software\ready-at-dawn-lone-echo\_local\saves\slot3\prevautosave0WaitableTimer slept too long/short (i.e. 3033.546874 ms) I went to the 'slot3' folder on the pool in Windows Explorer and found that the "autosave.radsave" file appears to be there, but when I try to read it or copy it, it is not there. I get a Windows error message saying "Could not find this item. This is no longer located in <PATH>". I went looking on the actual backing drives (not the pool) and found it on one of the archive drives. I was able to copy/read it just fine from there. Furthermore, I saw an error message in DrivePool stating that this file has a duplication conflict (like this). I find that strange, since this file is not duplicated. My hypothesis: the save game file was created during gameplay and since the SSDs are my write buffer, it was saved on one of them. Shortly later, DrivePool rebalanced it to an archive drive, and later for some reason when it tries to rename the file, it's not there anymore. I though maybe the game was sidestepping normal Windows copy APIs and therefore isn't compatible with drivepool, but I think that's not possible, since even Windows Explorer was having trouble with that file. Any suggestions? For now, I've just disabled real-time rebalancing and set it to happen overnight instead to reduce the chance of rebalance during gameplay.