March 3, 201412 yr I'm not a linux guru by any means....so, I suspect I'm looking at something wrong here. Unraid tells me my cache drive has 0b free on it. It's only a 40gb drive. the 3 shares I have set to use the cache drive all say they have 0b available. I beleive this is messing with some things in my sabnzbd configuration. I have sab installed to /mnt/cache/apps/sabnzbd - this folder is like...50mb tops there are folders with a . in front of them under tower/cache The only one I can find anything in is the /tower/cache/.sabnzbd folder I'm using windir stat to try to get sizes on my shares, but this one is blowing up to over 650gb......that's not possible on a 40gb drive. I've invoked the Mover a couple times, but nothing is freeing up disk space. I feel pretty dumb right now....can anyone help me? Thanks Matt
March 3, 201412 yr Author root@Tower:/# du -sh /mnt/cache/* 0 /mnt/cache/appdata 61M /mnt/cache/apps 0 /mnt/cache/cachetmp wtf, right?
March 3, 201412 yr Author root@Tower:/# df -h Filesystem Size Used Avail Use% Mounted on tmpfs 128M 2.2M 126M 2% /var/log /dev/sda1 3.8G 3.0G 855M 78% /boot /dev/md1 932G 828G 104G 89% /mnt/disk1 /dev/md2 932G 813G 120G 88% /mnt/disk2 /dev/md3 1.9T 1.3T 629G 67% /mnt/disk3 /dev/md4 932G 710G 222G 77% /mnt/disk4 /dev/md5 932G 252G 680G 28% /mnt/disk5 /dev/md6 1.4T 200G 1.2T 15% /mnt/disk6 /dev/md7 2.8T 1.4T 1.4T 50% /mnt/disk7 /dev/md8 932G 33M 932G 1% /mnt/disk8 /dev/hdd1 38G 38G 0 100% /mnt/cache shfs 11T 5.3T 5.2T 51% /mnt/user0 shfs 11T 5.4T 5.2T 51% /mnt/user
March 3, 201412 yr After some research, it seems du doesn't normally display hidden folders. Try it like this: cd /mnt/cache du -sch .[!.]* * |sort -h
March 3, 201412 yr Author After some research, it seems du doesn't normally display hidden folders. Try it like this: cd /mnt/cache du -sch .[!.]* * |sort -h this command is taking a LONG time. What value is set in your 'cache_min_free_space'? Where is that set? /dummy
March 3, 201412 yr After some research, it seems du doesn't normally display hidden folders. Try it like this: cd /mnt/cache du -sch .[!.]* * |sort -h this command is taking a LONG time. webgui 'share settings' What value is set in your 'cache_min_free_space'? Where is that set? /dummy
March 3, 201412 yr Author all 3 of the yellow folders (appdata, apps and cachetmp) are set to 0kb should I set them to 20971520? that's half of my drive...right? actually....appdata and cachetmp are both set to "no" under use cache disk, and apps is set to Only. A change I think I made last week......it used to be set to "no" also.....
March 3, 201412 yr Why do you have a folder called cachetmp set to not use cache? What is the purpose of this folder? That would explain why appdata and cachetmp are both showing as zero. They have been moved except for any hidden files. What are you using the 3 cache folders for? ls -al /mnt/cache/appdata and ls -al /mnt/cache/cachetmp
March 3, 201412 yr Author root@Tower:/mnt/cache# ls -al /mnt/cache/appdata total 0 drwxrwxrwx 2 nobody users 48 2014-02-27 22:44 ./ drwxrwx--- 10 nobody users 232 2014-02-26 09:49 ../ root@Tower:/mnt/cache# ls -al /mnt/cache/cachetmp total 0 drwxrwxrwx 2 nobody users 48 2014-02-27 22:45 ./ drwxrwx--- 10 nobody users 232 2014-02-26 09:49 ../ not much. it looks like that's where my sabnzbd runs, I have no idea honestly. You guys rule at unraid....I google stuff when I want something, then I typically follow instructions, then promptly forget about it. The next time something doesn't work or I have to reboot it, I have to re-learn some stuff.....I'm a shitty user....I hate having to support people like me at work. I'm ashamed.
March 3, 201412 yr It looks like those folders are truly empty. Do you really have something configured to use those folders? You can probably find them on another drive since they were moved by mover. My guess is that you didn't actually set these folders up to be a share in the GUI, but they became one because any folder at the root of the cache disk or any array disk is automatically a share to unRAID. Probably a lot that needs to be cleaned up but we should probably stick to one thing at a time. Lets back up a bit. ls -al /mnt/cache and ls -al /mnt/cache/apps
March 3, 201412 yr Author I really appreciate you helping me out man. root@Tower:/mnt/cache# ls -al /mnt/cache total 1 drwxrwx--- 10 nobody users 232 2014-02-26 09:49 ./ drwxr-xr-x 15 root root 0 2014-03-03 02:22 ../ drwxrwxrwx 2 root root 48 2014-02-25 22:29 .apps/ drwxr-xr-x 3 nobody users 72 2012-10-14 17:10 .couchpotato_v2/ drwxr-xr-x 18 nobody users 872 2014-02-26 02:52 .sabnzbd/ drwxrwxrwx 2 nobody users 48 2014-02-27 22:44 appdata/ drwxrwxrwx 4 nobody users 104 2014-02-27 22:37 apps/ drwxrwxrwx 2 nobody users 48 2014-02-27 22:45 cachetmp/ root@Tower:/mnt/cache# ls -al /mnt/cache/apps total 1 drwxrwxrwx 4 nobody users 104 2014-02-27 22:37 ./ drwxrwx--- 10 nobody users 232 2014-02-26 09:49 ../ drwxr-xr-x 18 root users 920 2014-02-25 23:00 sabnzbd/ drwxr-xr-x 10 root users 824 2014-02-10 20:00 sickbeard/
March 3, 201412 yr Author After some research, it seems du doesn't normally display hidden folders. Try it like this: cd /mnt/cache du -sch .[!.]* * |sort -h oh, this guy finished!! root@Tower:/mnt/cache# du -sch .[!.]* * |sort -h 0 .apps 0 .couchpotato_v2 0 appdata 0 cachetmp 61M apps 38G .sabnzbd 38G total
March 3, 201412 yr Well, I guess we see where the drive space has gone. 38G in .sabnzbd Looks like you probably setup some things to use hidden folders so they wouldn't get moved and also setup a cache-only share to run some of those same things in. Get me a screenshot of your SAB,SB,CP settings pages. We can probably find out where the folders for CP and SB have been moved with ls -al /mnt/user and repeat ls -al /mnt/disk1 for each of your data disks. I will have to step away for a while. Probably be back in about an hour.
March 3, 201412 yr 38G .sabnzbd Sounds like your SAB downloads folder didn't get cleaned out, and since it's a hidden folder, it didn't get moved to the array either. Can you browse your cache disk from your main computer? If so, set your file browser to show hidden files, and look around in the .sabnzbd/downloads folder and see if you can find the backlog of unprocessed stuff.
March 3, 201412 yr I think he must have reconfigured it to use a cache-only share and left behind all of the stuff in .sabnzbd
March 3, 201412 yr Author I can't find anything that points to that folder. my plugin says the install folder is: /mnt/cache/apps/sabnzbd my sab says: Default Base Folder: /mnt/cache/apps/sabnzbd Temporary Download Folder: /mnt/user/sabnzbd/Downloads/incomplete Completed Download Folder: /mnt/user/sabnzbd/Complete Post Processing Scripts: /mnt/user/Users/Matt/scripts nothing that points to .sabnzbd anymore. I think that might have been from when I had it in my go script and started it that way. I've had to kill it for a while because it'd start some old version with old history, then re-start it from the plugin (again, because I didn't know what I was doing). I did start from scratch with my go script recently, and so...that's not been happening anymore. do I need that folder? I bet I don't, but...I'm not gonna just delete it....yet
March 4, 201412 yr Well, it is taking up a lot of space, which was the original issue. But I still wonder if you have some misunderstandings. /mnt/user is all of the user shares. These are the combined contents of /mnt/cache root folders and /mnt/diskx root folders. This allows you to have shares that have part of their contents on cache temporarily and also span multiple disks. There is also /mnt/user0. This is the user shares without any of the contents that are still on cache. The mover script works by moving the /mnt/cache folders (except cache-only or hidden) to their corresponding /mnt/user0 folders. Probably a little more detail than you really wanted. If I haven't explained this well ask questions. In your case: /mnt/user/Users is a share named Users. Maybe this one was created by you intentionally. /mnt/cache/apps and /mnt/user/apps are the same thing, a share called apps. If it is set to cache-only it will reside on the cache drive and won't be moved by mover. /mnt/user/sabnzbd is a share named sabnzbd. How is this share configured? Did you intentionally create this share? If you haven't configured this share then unRAID configured it for you with default settings because it is at the root of /mnt/user. If you haven't set the sabnzbd share to cache-only it is on the array somewhere, causing your parity drive to get involved when things are written to it. You should probably be using a folder at /mnt/user/apps/sabnzbd instead of a separate sabnzbd share. The whole point of having a cache-only apps share is so you can put things in it that won't get moved and won't cause parity to get written. Any folder at the root of /mnt/cache, /mnt/user, or /mnt/diskx is treated as a share. If you didn't intend to create a share it happens anyway and gets default configuration, which means it can go on any disk except cache. Specifically, what you probably should have is a cache-only share named apps and then: Default Base Folder: /mnt/user/apps/sabnzbd Temporary Download Folder: /mnt/user/apps/sabnzbd/Downloads/incomplete Completed Download Folder: /mnt/user/apps/sabnzbd/Complete Check your other plugins also for similar inconsistencies.
March 4, 201412 yr Author again, I can't thank you enough for taking your time to help my dumb ass!!! I really do appreciate it! Well, it is taking up a lot of space, which was the original issue. But I still wonder if you have some misunderstandings. /mnt/user is all of the user shares. These are the combined contents of /mnt/cache root folders and /mnt/diskx root folders. This allows you to have shares that have part of their contents on cache temporarily and also span multiple disks. This I knew. There is also /mnt/user0. This is the user shares without any of the contents that are still on cache. The mover script works by moving the /mnt/cache folders (except cache-only or hidden) to their corresponding /mnt/user0 folders. This I didn't know, but it makes a lot of sense, and I appreciate the explanation. Probably a little more detail than you really wanted. If I haven't explained this well ask questions. In your case: /mnt/user/Users is a share named Users. Maybe this one was created by you intentionally. /mnt/cache/apps and /mnt/user/apps are the same thing, a share called apps. If it is set to cache-only it will reside on the cache drive and won't be moved by mover. /mnt/user/sabnzbd is a share named sabnzbd. How is this share configured? Did you intentionally create this share? If you haven't configured this share then unRAID configured it for you with default settings because it is at the root of /mnt/user. If you haven't set the sabnzbd share to cache-only it is on the array somewhere, causing your parity drive to get involved when things are written to it. You should probably be using a folder at /mnt/user/apps/sabnzbd instead of a separate sabnzbd share. The whole point of having a cache-only apps share is so you can put things in it that won't get moved and won't cause parity to get written. Any folder at the root of /mnt/cache, /mnt/user, or /mnt/diskx is treated as a share. If you didn't intend to create a share it happens anyway and gets default configuration, which means it can go on any disk except cache. Specifically, what you probably should have is a cache-only share named apps and then: Default Base Folder: /mnt/user/apps/sabnzbd Temporary Download Folder: /mnt/user/apps/sabnzbd/Downloads/incomplete Completed Download Folder: /mnt/user/apps/sabnzbd/Complete Check your other plugins also for similar inconsistencies. Yes, I created the users share, that's where I map the Family's "personal" drives to....it should be redone to be more secure, but...they don't seem to use it the way I'd like them to anyway. so if I use /mnt/user/apps/sabnzbd, sabnzbd would just be a folder in the "apps" share. Right? and the apps share SHOULD be left as a cache only disk? because changes to the app don't need to be causing the whole array to be spinning up and down, is that correct? Only the cache drive would be used until say sab finished downloading/repairing and extracting a movie? -and as i'm replying to each point in your post...I see in the last chunk that what I just said is exactly what you spelled out to me more explicitly in the last part. Why did I create these /.foldername directories? Did there used to be a time where Unraid would move any folder it could? but making it hidden with the . would prevent it from being "Movered" off the cache folder? I just keep digging deeper and depper into the /mnt/cache/.sabnzbd folder and there are so many dupe folders that I have to beleive there is some kind of Symbolic Links or something....For example: I keep using that command you gave me "du -sch .[!.]* * |sort -h" which seems to dig down list every folder I have and how much space it's using. right now I'm down to /mnt/cache/.sabnzbd/mnt/user/.sabnzbd which has another "user" folder which has another .sabnzbd folder and it kinda goes on....any chance of something like that? I kinda just want to rename that .sabnzbd but it's a beast and doing stuff with it is taking forever. thanks so much again!
March 4, 201412 yr There was a time (pre v5 I think) when unRAID did not have cache-only shares. But since mover ignores hidden (.) folders you could get the same effect by creating hidden folders on cache. The disadvantage of this is that they were hidden and it wasn't always easy to get some things to see them. Hidden folders on cache are still ignored by mover, but cache-only shares are better and the recommended way to do this now. That du command I gave you is just something I found and it's not clear to me exactly how it works. You could just use cd and ls to get some idea (slowly perhaps) of what is in that folder. If you think there is something worth saving in it you might figure out how to use the find command to get what you're after. Do you know about midnight commander? Just type mc at the command line and you will get a 2-pane "file explorer".
March 4, 201412 yr Author I've used mc before, but it's been a long time. reminds me of something i used to use pre Win3.11. Lol, I've been doing computers a long time, but messing with linux...beyond just messing with it has never really been a driving force for me. Looking through /.sabnzbd I'm not seeing any dates after 2-26-2014, I beleive that's the day I bailed on my old go script and wiped out as much as I could to start over again, after I upgraded from Unraid 5 beta 14 to 5.05. I think I started with 4.6, so......that sounds like it's probably where those .anything folders came from. i'm thinking about trying to move that whole /mnt/cache/.sabnzbd to another folder and reboot....see if anything's broken beyond repair. I'm such a hoarder...I'd hate to lose my sabnzbs history. why am I like that!? I did find about 8gb burried in there that seemed to be my old Plex Library....deleted it and got back about 8gb of that cache drive. F these .hidden folders...what a pain in the butt they are. cache only share is the way to go! OTOH, if my Plex library is ~8gb, that's almost a quarter of my cache drive....I'm wondering what the downside would be to keeping Plex on a regular (spanned across all disks) share..... what do you think? is my thought process completely insane here?
March 4, 201412 yr Plex is especially known to keep drives spinning so I think most people keep it on cache. Probably a better idea is to have something which automatically backs up your cache to the array periodically, but to do it right you need to stop the processes that are using it then do the backup then restart them. Here is a thread that talks about that. I really need to implement something like this myself but I have moved on to virtuals for most of this and my configuration is evolving.
March 4, 201412 yr When you access sabnzbd via its web interface, you'll see a bunch of 'broken' downloads on the bottom half of the main screen. When you delete those broken links, be sure to select 'PURGE FAILED NZBS and DELETE FILES', that will clear out the un-complete-able trash downloads.
Archived
This topic is now archived and is closed to further replies.