V4.7 Pro

 

Free space is 2.2tb.

 

When I open the File Browser page, I have this:

 

/mnt/user/_TV/ (empty)

 

/mnt/user/TV/ (holds everything)

 

When browsing with Total Commander, I have files in \\Tower\cache\TV\The.Soup

 

The same files are in \\Tower\TV\The.Soup

 

I copied a file out of the cache folder back to my desktop, and it disappeared from the array folder.

 

More info, again in File Browser:

 

http://tower:8080/file_browser?dir=/mnt/user/TV/

 

http://tower:8080/file_browser?dir=/mnt/user/_TV/

 

The second (_TV) folder is empty, according to File Browser.

 

Yesterday, I was able to use Mover without error. About 20gb of data was moved from _TV/parent.folder to TV/parent.folder. Easy peasy. It would seem like I've done something wrong here in the configuration of Mover, or the directories that are associated with Mover.

 

Mainly though, I'm concerned why something done to a cache folder of the same name (except for the _) effects an array folder of the same name.

TV is a share so \\Tower\TV is the view of the share including the cache disk and \\Tower\cache\TV is a view of the share data stored on the cache disk.

 

I have no idea how _TV has anything to do with TV. This should be a different share and work independently of the TV share. However, maybe the "_" confuses unRAID.

 

Peter

TV is a share so \\Tower\TV is the view of the share including the cache disk and \\Tower\cache\TV is a view of the share data stored on the cache disk.

 

I have no idea how _TV has anything to do with TV. This should be a different share and work independently of the TV share. However, maybe the "_" confuses unRAID.

 

Peter

 

If I change the Share named _TV to NOT use cache disk, will that remedy the issue?

OK, you described some shares and put links to your internal server that we can't see and a description of some mover use that doesn't really make any sense. The end result is that I don't understand your problem.

 

Yesterday, I was able to use Mover without error. About 20gb of data was moved from _TV/parent.folder to TV/parent.folder. Easy peasy.

 

This makes no sense. The mover should not move anything from _TV to TV yet you seem to imply that's what you want it to do???

 

Why do you have a TV share and a _TV share anyways?

 

Peter

Thanks for posting again even though you don't understand what I'm asking. I think new users are at a disadvantage not knowing enough to ask for help succinctly and correctly.

 

The links are to illustrate the exact path of the dirs. It's not for anyone to click and see what's there. I simply added that the mover worked yesterday to let people know it did work.

 

The main issue is duplication of files across \\Tower\cache\TV\The.Soup and \\Tower\TV\The.Soup. Then I remove a file from \\Tower\cache\The.Soup, it is also removed from \\Tower\TV\The.Soup.

 

They don't appear to be the same dir, but are acting as if they are because deleting files from the cache dir also removes them from the array dir.

 

 

They both link to the cache disk.

 

\\Tower\TV is the content of the TV directory on every array disk (including the cache disk) combined into one common network location.

 

\\Tower\cache\TV is the content of the TV directory on the cache disk, which will also show when you go to \\Tower\TV.

 

If you go to \\Tower\disk1\TV you will also find content that appears in \\Tower\TV. Same with any other disk holding TV. Each disk holds part of the \Tower\TV contents. This is what user shares do.

 

When you copy data to \\tower\TV the data is first copied to the cache disk and then moved to an array disk. So, both before and after the move when you access \\tower\TV you see the same data.

 

What did "_TV" have to do with the question?

 

Peter

 

Being new, I did not know the cache disk was linked to the array in that manner. I thought they worked together, but more independent.

 

The fast transfer rate last night confirms what you say about data going to cache first.

 

I could not figure out why _TV had the same data as TV, so I asked.

 

I just invoked the mover and data is being moved. After the mover completes, is it safe to delete the dupe files on cache?

Could this be what happened?

 

A large amount of data transferred from my machine to the cache drive did not complete before the mover began its process. I've read that any file being written cannot be moved. So, all of these files were moved onto the cache (also visible in the array), and were waiting for the next move cron?

Yes, that's possible. Or, you moved that data after the mover ran.

 

I have no idea what the _TV is. I think it might be a rogue share you have on the server. Does it appear as another share when you go to the Shares management page? Does it appear as a directory on any of the data disks or cache disk? Did you create a _TV directory one a disk or create a _TV user share for some reason?

 

Peter

I thought I read somewhere that \.TV would not be able to be processed by mover. So the \_TV was created in instead. Once this current transfer completes, I'll remove it and then try and figure out where to send completed SAB downloads to so they get processed. THAT is the final frontier.

 

1) Click the nzb file on the web

2) It's added to SAB

3) Download and extract to * folder

4) Mover starts and checks out * folder

5) It moves the new downloads to somewhere

 

I'm not sure how mover fully works yet. See above. I thought I had to re-create (in _TV directory) all the folders of the array (TV directory), move the new files to those _TV sub-folders, then only would the mover move them into the same named folder on the array.

 

You don't do anything special to use the cache disk on the server. Just move the files to /mnt/TV and the server will first place them on the cache disk and move them later.

 

Run Sickbeard and it will do the whole process automatically.

 

Peter

You don't do anything special to use the cache disk on the server. Just move the files to /mnt/TV and the server will first place them on the cache disk and move them later.

 

Run Sickbeard and it will do the whole process automatically.

 

Peter

 

So that's a nuance I did not realize before. It sounds like I saw the files in "two" locations and freaked out. When in fact, they were waiting for the next mover cron to be "removed" from the cache drive and simply left in place on mnt/tv. Holy shit, a breakthrough.

 

Now, to set my cron job for more than once a day!

 

Thanks again, Peter, for sticking with me on this.

I was thinking of adding to the Wiki page about mover, so someone else as easily confused as I is also not sucking air trying to get all of this going.

 

Something like this:

 

"Once the cache drive is installed and in use, visit the Shares page and specify which individual Shares should "Use cache disk". Set a free space amount (in kB; I use 3145728 or 3gb). Finally, the steps to utilize the mover script are actually nothing special. The process is identical as it was prior to installation of the cache drive. Simply transfer files to the same location as before; tower/tv, tower/movies, whatever it was. The files will sit on the cache drive and then be "moved" when the mover script runs. By default it runs at 3:40 am each day.

**CAUTION** While the files are being transferred (and also when they have completed the transfer), both the cache disk and the array will display the new files. Only after the mover script has completed will the files only be listed in the array. Take care not to delete either set thinking they are duplicate files, as ALL data will be gone. Once the mover has run, the cache "duplicates" will be gone. Your syslog will display progress and errors, if they present."

 

I use a cron job schedule that runs the mover every 12 hours:

* */12 * * *

 

Anything in there that is flat out wrong, or can be improved?

I don't like the working of the warning. The cache works like any data disk as far as the sharing is concerned. Also, it's not duplicated data. You can go to \tower\disk1\TV and \tower\disk2\TV and find "duplicates" that are also in \tower\TV.

 

Maybe something more along the lines of the data being put in a temporary share on the cache disk which later gets moved to the protected disks and deleted.

 

Peter