I'm finally done with copying data off my USB drives and now I am looking forward to start storing new HD files directly to my Unraid. Base on what I read so far, cache disk doesn't work unless you have User Share enabled. Is there a workaround to copy files directly to the disk#?

 

Currently, this is what I have for my disks.

 

//disk1/MyMovies/Kids

//disk2/MyMovies/Action

//disk3/MyMovies/Drama

//disk4/..........

 

If there's no workaround to copy files directly to disk# off cache disk, does the following User Share make sense.

 

Share name: Kids

Allocation method: High-water

Split level: 1

Included disk(s): disk1

Excluded disks(s):

Use cache disk: Yes

Export mode: Export read/write

 

Share name: Action

Allocation method: High-water

Split level: 1

Included disk(s): disk2

Excluded disks(s):

Use cache disk: Yes

Export mode: Export read/write

 

Share name: Drama

Allocation method: High-water

Split level: 1

Included disk(s): disk3

Excluded disks(s):

Use cache disk: Yes

Export mode: Export read/write

 

 

For the cache disk, I will create the following directory.

//Kids/this_<foldername>_will_copy_to_disk1

//Action/this_<foldername>_will_copy_to_disk1

//Drama/this_<foldername>_will_copy_to_disk1

 

Is this how cache disk work?

 

BTW, I just ordered a 2.5 WD 500GB for my PS3 so I can use the 60GB for my Unraid. :-)

 

thanks in advance,

~joy

 

 

Only top level folders will be created as user-shares.  Currently you only have one top level folder.  It is MyMovies.  It would be your only user-share.

 

Your proposal will work, with three shares, each with a specific "included" disk.  But... the cache disk does work as you think.  Once enabled, it is completely transparent to you.  You do not need to create folders on it, and when the files and folders on it are created by unRAID, they will have the same exact paths and names as on the data disks.

 

So... if you have a cache drive defined, and it has the space needed for a file, when you create a new file in

//tower/Kids

it will be created in

/mnt/user/cache/Kids

Later that night, it will be moved to

/mnt/disk1/Kids

based on your share allocation rules.

 

During the interim, until it is moved, it is still accessible at \\tower\Kids as if it was in the parity protected array, even though it is not protected by parity until it is moved.

 

So, everything you are planning is correct other than you not needing to create any directories on the cache drive.

 

Joe L.