Single filesystem containing two storage objects and their locations. Resembles a reversed NTFS junction.
Single filesystem containing two storage objects and their locations. Resembles a reversed NTFS junction.
I need to inform the system about this folder named 'C:\Parent'. When you create a file, remember to save it in both the Dropbox location and the local SDD folder. It's frustrating because the RAID array is slow and inefficient. My main goal is to speed up the process, but I'm facing several challenges along the way.
This feature isn't available on Windows. Raid operates at a block level rather than a file level, meaning an entire filesystem must be configured in one level of RAID. You might manage syncing through third-party tools, keeping new footage on your SSD while preventing updates from being sent to Dropbox. Then modify the local copy on your SSD and transfer the final files when finished.
You can attach drives (and raid volumes) to folders rather than using drive letters in Windows. This offers only a limited solution, but it enables a raided folder on another storage device.
The problem arises because the syncing program attempts to move files from HDDs to SDDs during download, which delays both tasks significantly. Understanding this better could clarify why it’s happening.
It should stay until the download finishes. You can either let the lock disappear or wait until the file is closed. It shouldn’t be a complicated script.
I addressed the issue thoughtfully. I was mainly discussing "can I raid a folder." You can configure your C:\parent folder as a separate raid 1 array. However, this still leaves challenges with simultaneous downloads and copies. You’d need a raid 1 that’s fast enough for direct work—likely an external Thunderbolt RAID 1 NVMe setup. Or you could download the files to it, store them on your NVMe drive, and then transfer them back. It feels like a bit of a loop. Perhaps consider a NAS that can automatically sync Dropbox files locally. You’d still need to copy files in and out for processing, but the NAS would stay updated without your input most of the time.
I might need to take a different path. It's puzzling how NTFS doesn't support this feature directly—it's almost the opposite of an NTFS Junction. I attempted to use software tools, but it was tough figuring out what property to check for progress. What do you mean by this "lock"?