ridley Posted August 12, 2022 Share Posted August 12, 2022 Recently I have been getting execution errors on starting or stopping dockers. Doesn't seem to occur on anyone in particular, and does happen on dockers that have worked for years. Also if I have dockers enabled building parity or a drive is incredibly slow 20MB/s or less, whereas disabled it is 130Mb/s. Any idea what is causing it? tower-diagnostics-20220812-1957.zip Quote Link to comment
trurl Posted August 12, 2022 Share Posted August 12, 2022 Your docker setup is way off. appdata is all over the array. Can't quite figure out system share since there seems to be more than one of them but they are both on the array also. 400G docker.img is at least 10 times larger than anybody needs. Not clear where that is since your system share is unclear as mentioned, but probably on the array. Disable docker in Settings for now, lots of things to clean up. Go to User Shares page, click Compute All button at bottom, wait for the results to complete. If you don't have complete results after a few minutes, refresh the page. Then post a screenshot. Quote Link to comment
ridley Posted August 12, 2022 Author Share Posted August 12, 2022 Will do. Is this perhaps because I recently added a cache drive? Quote Link to comment
trurl Posted August 13, 2022 Share Posted August 13, 2022 18 hours ago, ridley said: I recently added a cache drive? That would explain why these shares have files on the array. You do have 2 "system" shares, as you can see, but one of them is named "System". Linux is case-sensitive, so these are different shares with different paths. The usual naming for that is "system". We need to find out what is in "System" That screenshot is not the complete results. When the results are complete, each share will show how much of each disk is used by the share. Maybe you only did Compute... on appdata instead of Compute All button? Try again. Quote Link to comment
ridley Posted August 13, 2022 Author Share Posted August 13, 2022 1 hour ago, trurl said: That would explain why these shares have files on the array. You do have 2 "system" shares, as you can see, but one of them is named "System". Linux is case-sensitive, so these are different shares with different paths. The usual naming for that is "system". We need to find out what is in "System" That screenshot is not the complete results. When the results are complete, each share will show how much of each disk is used by the share. Maybe you only did Compute... on appdata instead of Compute All button? Try again. Is that any better? Thanks for all your help shares.pdf Quote Link to comment
trurl Posted August 13, 2022 Share Posted August 13, 2022 I recommend NOT sharing disks. Several ways to get yourself in trouble with that. And since you have Dynamix File Manager plugin, you can manage files on the disks anyway, and it won't let you get in trouble. What do you get from the command line with this? ls -lah /mnt/user/System and this? ls -lah /mnt/user/system Quote Link to comment
trurl Posted August 13, 2022 Share Posted August 13, 2022 Or if you'd rather you can just use the webUI to drill down into System and system shares and post screenshots of the contents Quote Link to comment
ridley Posted August 13, 2022 Author Share Posted August 13, 2022 2 hours ago, trurl said: I recommend NOT sharing disks. Several ways to get yourself in trouble with that. And since you have Dynamix File Manager plugin, you can manage files on the disks anyway, and it won't let you get in trouble. What do you get from the command line with this? ls -lah /mnt/user/System and this? ls -lah /mnt/user/system Quote Link to comment
ridley Posted August 13, 2022 Author Share Posted August 13, 2022 1 hour ago, trurl said: Or if you'd rather you can just use the webUI to drill down into System and system shares and post screenshots of the contents Quote Link to comment
trurl Posted August 13, 2022 Share Posted August 13, 2022 Any idea what all that in System folder is? Looks more Windows related than Unraid. Quote Link to comment
ridley Posted August 13, 2022 Author Share Posted August 13, 2022 13 minutes ago, trurl said: Any idea what all that in System folder is? Looks more Windows related than Unraid. No idea, looks like Windows stuff to me and hasn't been modified for a 1/4 century.... I suspect some backup of a windows folder from way, way back. Quote Link to comment
trurl Posted August 13, 2022 Share Posted August 13, 2022 If you don't know what it is I guess you don't need it. In any case, you don't want a user share named System. Delete or move the contents, then delete the System user share. Of course you want to keep the system user share. In addition to Docker disabled in Settings, you also need to disable VM Manager. Do you have any VMs? Quote Link to comment
ridley Posted August 13, 2022 Author Share Posted August 13, 2022 What to do with the APPDATA? Quote Link to comment
trurl Posted August 13, 2022 Share Posted August 13, 2022 1 minute ago, ridley said: What to do with the APPDATA? Fortunately you don't have a share named APPDATA. You do have an appdata share. We will deal with it at the same time we deal with system share. 1 hour ago, trurl said: you don't want a user share named System. Delete or move the contents, then delete the System user share. Of course you want to keep the system user share. In addition to Docker disabled in Settings, you also need to disable VM Manager. Do you have any VMs? If you have done all that post new diagnostics. Quote Link to comment
ridley Posted August 13, 2022 Author Share Posted August 13, 2022 1 hour ago, trurl said: If you don't know what it is I guess you don't need it. In any case, you don't want a user share named System. Delete or move the contents, then delete the System user share. Of course you want to keep the system user share. In addition to Docker disabled in Settings, you also need to disable VM Manager. Do you have any VMs? Disable the VM whilst sorting out the APPDATA you mean? Quote Link to comment
ridley Posted August 13, 2022 Author Share Posted August 13, 2022 22 minutes ago, trurl said: Fortunately you don't have a share named APPDATA. You do have an appdata share. We will deal with it at the same time we deal with system share. If you have done all that post new diagnostics. Diagnostics tower-diagnostics-20220813-2216.zip Quote Link to comment
trurl Posted August 14, 2022 Share Posted August 14, 2022 Set appdata and system shares to cache:prefer, domains is already cache:prefer and all on cache. You want those shares all on fast pool (cache) and set to stay there so dockers/VMs aren't impacted by slower array, and so array disks can spindown, since these files are always open. Then run mover, let it complete, and post new diagnostics. Nothing can move open files, so that is why Docker and VM Manager has to be disabled. And mover won't move duplicates, so there may be some manual cleanup left to do. Quote Link to comment
ridley Posted August 15, 2022 Author Share Posted August 15, 2022 16 hours ago, trurl said: Set appdata and system shares to cache:prefer, domains is already cache:prefer and all on cache. You want those shares all on fast pool (cache) and set to stay there so dockers/VMs aren't impacted by slower array, and so array disks can spindown, since these files are always open. Then run mover, let it complete, and post new diagnostics. Nothing can move open files, so that is why Docker and VM Manager has to be disabled. And mover won't move duplicates, so there may be some manual cleanup left to do. Been running mover for 12+ hours now and it is very, very slow. I am talking a MB / s slow, that cannot be right, right? Quote Link to comment
Kilrah Posted August 15, 2022 Share Posted August 15, 2022 If appdata contains lots and lots of tiny files it can. That's why you don't want that on the array, accessing those can be very slow on HDDs. 1 Quote Link to comment
ridley Posted August 15, 2022 Author Share Posted August 15, 2022 (edited) 2 hours ago, Kilrah said: If appdata contains lots and lots of tiny files it can. That's why you don't want that on the array, accessing those can be very slow on HDDs. I think you're right, it seems to have got to bigger files and is now up to 100MB/s and now back to very slow 🙂 Edited August 15, 2022 by ridley Quote Link to comment
ridley Posted August 15, 2022 Author Share Posted August 15, 2022 22 hours ago, trurl said: Set appdata and system shares to cache:prefer, domains is already cache:prefer and all on cache. You want those shares all on fast pool (cache) and set to stay there so dockers/VMs aren't impacted by slower array, and so array disks can spindown, since these files are always open. Then run mover, let it complete, and post new diagnostics. Nothing can move open files, so that is why Docker and VM Manager has to be disabled. And mover won't move duplicates, so there may be some manual cleanup left to do. OK it has finished and here are the diagnostics tower-diagnostics-20220815-1740.zip Quote Link to comment
trurl Posted August 15, 2022 Share Posted August 15, 2022 Still a lot of appdata all over your array, and system also still on array disks. Even though it is mounted, corruption logged on disk24. Many of your disks are very full. Why don't you have dual parity with so many disks? Post a screenshot of Array Devices Quote Link to comment
trurl Posted August 15, 2022 Share Posted August 15, 2022 And why is nothing assigned as disks 8-14? Quote Link to comment
ridley Posted August 15, 2022 Author Share Posted August 15, 2022 2 minutes ago, trurl said: And why is nothing assigned as disks 8-14? 8-15 you mean? I removed them and replaced them with larger drives after a bit of unbalancing. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.