As Stated....

How are edits to files handled when using cache drive once the files are moved to the unraid array?

Currently running raid 0 WD black 1tb as cache (2TB)

 

 

Thanks

Wes

 

 

 

If accessing files through the user share you will not notice if the file is on the cache or the array.

Of course there might be speed differences, but the point is that you access the file at the same place at all times.

Are they re written to cache drive when you edit the file?

Is the File moved from unraid array back to cache when edited? ( a save from a ms program per say )

or once the file is moved to the unraid array it lives there for good...

if the cache drive is back in play is file removed from unraid array?

 

I believe they're edited in place, wherever that is.  No file is moved if it's in use.  You are editing /mnt/user/SHARE_NAME/FILE_PATH/FILE_NAME, and it doesn't matter where it's currently stored.  New files are stored according to the share's settings, which may or may not include storing it on the Cache drive.  But the path to the file is still through /mnt/user, which is a virtual file system, on top of the real file systems on the data drives and the Cache drive.

 

I don't recall anyone ever having a problem with this.  What in particular are you worried about?

I work with allot of solid works part and assembly files with some assembly files having large amount of part files linked

Main Concern is if I save file after edit it is moved back to cache is that it is unprotected raid 0 failure ( working on changing to raid 10)

But I loose speed with the write to array when I start modifying files if once the mover is used files are moved to array and live there.

I am trying to make my solid work experience and large assemblies load faster. (going for multi drive btrfs raid 0 or raid 10 array )

 

Currently I am using unraid as back up server for our workstations with nightly incremental backups.

As we are growing looking to continue using unraid however with more of us working on solid works we need a pooled access to files.

I really like the btrfs storage flexibility and I am debating just using custom mover (r sync) to back up the working directory every x minutes that looks at last modified and moves it to unraid array similar to mover if file is x old user/ to user0/.

 

Thank you for your reply's

Wes

 

 

 

 

 

Probably better than going RAID 0 is going to a Cache Pool of high performance SSD's.  That will give you the fastest speeds plus fault tolerance.

Ya I am thinking that route... or btrfs raid 10 in cache pool with 4 ssd.

Now the fun part... I would like the files to live there on cache pool for 2 weeks

then rsync to unraid array if files older the 2 weeks.

Can this still look seamless to end user? ( user/working user0/working)

 

 

 

You can modify the Mover script.  Or use your own script based on the Mover script.