October 14, 20169 yr I deleted some backup file which I apparently made myself and kept on the /mnt/cache/, so for now the Dockers boot fine again. But, what is going on? The Cache pool normally doesn't go much beyond 50% of it's capacity. And why didn't it move stuff over to the Array? Is there some log that possibly traces this? Cheers, Arndoid
October 14, 20169 yr I deleted some backup file which I apparently made myself and kept on the /mnt/cache/, so for now the Dockers boot fine again. But, what is going on? The Cache pool normally doesn't go much beyond 50% of it's capacity. And why didn't it move stuff over to the Array? Is there some log that possibly traces this? Cheers, Arndoid Diagnostics along with postings of the volume paths for every docker app is what is really needed here
October 14, 20169 yr Also for the cache pool, see if your shares are set to use cache or to prefer cache. I filled up mine accidentally with having preferred on.
October 14, 20169 yr Author As for my shares, I have my all shares say No to Cache, except for the following: My own shares: Downloads/Movies/Series (For extracting of files, performance) - Yes UnRAID's default shares: appdata (says: application data) - Only domains (says: saved VM instances) - Only system (says: system data) - Only As for the Diagnostics, see attachments. Edit: Docker Volume paths: https://i.imgur.com/HNObRAE.png Edit 2: Squid, I installed your Ransomware Protection and User Scripts plugins, thanks a ton for creating these man. unimatrix_zero-diagnostics-20161014-1454.zip
October 14, 20169 yr Hard to say since mover never ran (nor was it scheduled to run) during the time period covered by the syslog (it runs @ 3:40am) But, since you're using /mnt/user as a reference for the appdata shares (with a floor setting of 64G and use-cache=only), once your 128G pool drops below 64Gig available, you are out of disk space. You can change your appdata share within the containers to say instead /mnt/cache/appdata, and it'll override the cache floor settings, to allow your containers to run (or lower the floor setting) What happens if you manually run mover? (ie: post diagnostics after hitting the button if nothing happened)
October 14, 20169 yr Author If I run Mover (Settings > Schedule > Mover Settings), clicking the button "Move now" doesn't show me anything but a quick page refresh. Cache pool's free space doesn't seem to change. https://i.imgur.com/ClDuthz.png
October 15, 20169 yr Author It's been 3:40AM, and I tried running the Mover manually. Maybe the issue can be found in the diagnostics this time around. (See Attachment) unimatrix_zero-diagnostics-20161015-1327.zip
October 15, 20169 yr Author Check Disk Filesystems Alright, I followed the instructions. First, as it required no maintenance mode, I scrubbed my BTRFS cache pool, everything seems fine. In maintenance mode, I ran the xfs_repair status, with the -nv parameter. Disk1: Phase 1 - find and verify superblock... - block cache size set to 1475256 entries Phase 2 - using internal log - zero log... zero_log: head block 1115756 tail block 1115756 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Sat Oct 15 16:24:28 2016 Phase Start End Duration Phase 1: 10/15 16:24:19 10/15 16:24:19 Phase 2: 10/15 16:24:19 10/15 16:24:19 Phase 3: 10/15 16:24:19 10/15 16:24:24 5 seconds Phase 4: 10/15 16:24:24 10/15 16:24:24 Phase 5: Skipped Phase 6: 10/15 16:24:24 10/15 16:24:28 4 seconds Phase 7: 10/15 16:24:28 10/15 16:24:28 Total run time: 9 seconds Disk2: Phase 1 - find and verify superblock... - block cache size set to 1475256 entries Phase 2 - using internal log - zero log... zero_log: head block 1229226 tail block 1229226 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Sat Oct 15 16:26:16 2016 Phase Start End Duration Phase 1: 10/15 16:26:09 10/15 16:26:09 Phase 2: 10/15 16:26:09 10/15 16:26:09 Phase 3: 10/15 16:26:09 10/15 16:26:14 5 seconds Phase 4: 10/15 16:26:14 10/15 16:26:14 Phase 5: Skipped Phase 6: 10/15 16:26:14 10/15 16:26:16 2 seconds Phase 7: 10/15 16:26:16 10/15 16:26:16 Total run time: 7 seconds Disk3: Phase 1 - find and verify superblock... - block cache size set to 1475264 entries Phase 2 - using internal log - zero log... zero_log: head block 3382858 tail block 3382858 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Sat Oct 15 16:26:59 2016 Phase Start End Duration Phase 1: 10/15 16:26:53 10/15 16:26:54 1 second Phase 2: 10/15 16:26:54 10/15 16:26:54 Phase 3: 10/15 16:26:54 10/15 16:26:57 3 seconds Phase 4: 10/15 16:26:57 10/15 16:26:57 Phase 5: Skipped Phase 6: 10/15 16:26:57 10/15 16:26:59 2 seconds Phase 7: 10/15 16:26:59 10/15 16:26:59 Total run time: 6 seconds As instructed, I did not scan my Parity drive. But, everything seems fine, right?
October 16, 20169 yr Author It didn't seem to do much neither, cache pool still doesn't clear itself.
October 16, 20169 yr Author Alright, so, UnRAID doesn't offload my cache. Is there anything I can do?
October 16, 20169 yr Possibly stupid questions, but what shares is it supposed to be moving off of the cache? Are there files on the cache in those shares?
October 17, 20169 yr Author Haha, no problem, I'm taking all the help I can get, this is my server for that matter. My own shares: Downloads/Movies/Series (For extracting of files, performance) - Yes UnRAID's default shares: appdata (says: application data) - Only domains (says: saved VM instances) - Only system (says: system data) - Only Other shares that I have are on No to cache. The files that I can find in "/mnt/cache/" can also be found in "/mnt/user/".
October 17, 20169 yr The files that I can find in "/mnt/cache/" can also be found in "/mnt/user/". /mnt/user is the files on your array including the cache drive /mnt/user0 is just the files on your array WITHOUT the cache drive..
Archived
This topic is now archived and is closed to further replies.