I removed a 1tb drive (unused) from the array. Reinstalled as a cache. All went well (info from here helped a lot).

 

I am not sure I understand its use.

 

    I set one of the array's SMB shares to use the cache drive to test. The SMB share is software.

    I then copied a file into the SMB share (software) I noted the file was in the SMB share, and the cache drive had a dir created with the same file in it. both the file in the share in the array and the file in the cache had the same file size. I then forced the mover to run and the dir and file was removed from the cache drive.  I assume this is correct operation?

 

Would someone please advise.

 

Thanks

 

Ed

 

   

 

Yes that is what is supposed to happen.

 

When a file is copied to a share on the array, when cache drive is set it puts the file on the cache drive. There is no parity protection for the file so if the cache drive dies the data goes with it.

The file will be visable as if it were part of the array.

The mover script (which most people run in the middle of the night) then moves the file onto a disk in the array and adjusts parity to match so the file then has parity protection.

 

Josh

Out standing Josh.  Thanks for the quick response.

 

If I install a applican/program on the cache drive, do I have to place a '.' in frot of each file folder to prevent the mover from moving it?

 

Again thanks.

 

Ed

 

 

Under 4.7 you need to dot or you can install an unmenu package that allows you to use an _

 

The latest beta allows the creation of cache-only shares.

I have a dot on mine but just be aware that windows will see it as a hidden folder.

 

Josh

I have a dot on mine but just be aware that windows will see it as a hidden folder.

 

Josh

And so will OS X