I am embarrassed to be asking this but I am tired and after searching for an hour I am running out of patience and figured someone knows an easy solution to this (is there ever an easy solution with unRaid?).

 

I noticed today that my sabnzbd (installed on unRaid, using a cache drive) downloads had stopped because I am low on space on my cache drive.  For some reason my mover script doesn't appear to be moving files anymore, or at least that is my best guess.

 

That leads me to a few questions of things that are easy on a windows/mac/ubuntu but I just have no idea how to do on unRaid.

 

1.  How do I find space used on the cache drive?  I tried variations of du and ls, the disk usage script, as well, using Mac Finder, Midnight Commander, and the AjaxPlorer plugin but couldn't find a version that would show me in a readable format where my disk space has gone.

 

2.  Once I figure out where my space has gone, how do I move files from my cache drive to my main shares?  I did run into a ton of empty folders, as if my mover script is moving files but not folders.  Not idea how to move those or clean them up. 

 

Is there an easy way to select and move a bunch of files at once?  Something gui based would be awesome, in Windows this takes minutes using windirstat and exploer, on a Mac it's minutes using DaisyDisk and Finder, what would I do in unRaid?  I tried connecting via FTP even hoping I could connect that way (I read there was a built in ftp server in unRaid 4.7 which I am using) but wasn't able to connect via FTP.

 

Is this an easy thing to do that I am just missing, or is it just one of those things that is difficult in unRaid?

 

-Shane

Also, my syslog is full of duplicate file messages from the mover script.  Can anyone tell me how I ended up with duplicate files, and how I get rid of them?  Is this a bug in the mover script, does it end up sometimes copying files instead of moving them?

 

 

I think I am getting closer, figured out how to multi-select files and move them in Midnight Commander but I am not sure where to move them to.  I have two directories that appear to hold my user shares, /mnt/user/MyShares and /mnt/user0/MyShares.  Is one of these the correct one?  Will I screw things up or just lose my files if I move them from the cache drive into /mnt/user/MyShares, in other words, is this like moving them right on top of themselves since the writes to the user shares will just go to the cache drive anyway?

Until you get things under control, I'd advise setting your disk shares and cache drive to export visible, and map them all to drive letters on a windows box if you are comfortable working that way.

 

The quick and easy way to do that is with the net use command, something like this.

net use p: \\servername\disk1

net use q: \\servername\disk2

....

net use z: \\servername\cache

 

Use windirstat, clonespy, and explorer to check things and move things around from disk to disk, keeping in mind that all root level folders on the drive shares will become user shares. Duplicate files happen when multiple disks contain identical file names and full paths. Once you can examine the individual disk shares, you rename or delete the identical named files depending on whether or not the contents are identical. Clonespy is good at finding duplicate names and or content, but you have to point it at the individual drive shares. The user shares will never show more than the first disks copy of any dupe file name in the same folder, whatever the content.

That was very helpful, thank you.  I had no idea I could export the cache drive like that.

also to add, use treesize on the cache drive (itwill tell you whats taking up storage on the disk)

 

you dont have to map a drive for treesize, you can unc to it "\\tower\cache"

 

Nick

 

also to add, use treesize on the cache drive (itwill tell you whats taking up storage on the disk)

 

you dont have to map a drive for treesize, you can unc to it "\\tower\cache"

 

Nick

windirstat does the same thing, and no, you don't HAVE to map drive letters to work on them, it just makes it easier in some utilities. I'd rather type n: than \\servername\disk if I'm specifying a location to work on. You can always disconnect the mappings when you are done. Personally, I leave the disk exports on but hidden, and use drive to disk mapping on one machine to manage things, and the rest of the network only uses the user shares, some read only, depending on need.