![]() See the image information of 8ed7463b8476. Hello-world latest fce289e99eb9 2 years ago 1.84kB The images should stored in /var/lib/docker/overlay2 by default. You can manually set the storage driver with the -s or -storage-driver= option to the Docker daemon. In most places this will be aufs but the RedHats went with devicemapper. If you search the help for "Miscellaneous used space" you can find the following: GrandPerspective actually features quite extensive help documentation.The contents of the /var/lib/docker directory vary depending on the driver Docker is using for storage.īy default this will be aufs but can fall back to overlay, overlay2, btrfs, devicemapper or zfs depending on your kernel support. "Miscellaneous used space: All used space that is not accounted for by the size of the scanned files. Low-level file system data, needed to store amongst others the folder hierarchy." This includes the following:įiles that were not scanned, either because the scanned folder was not at the root of the volume, or the user did not have permissions to access all subfolders.įiles that are excluded by the filter (if any).ĭisk space that is not accounted for because the Logical file size measure is used, which underestimates the space that files actually take up. To reduce the size of the miscellaneous used space, you can do the following:ġ) Run GrandPerspective as "root" so you have permission to scan all files (see )ģ) Scan in the entire HD, without using a filter That should, as far as I can see, really keep the miscellaneous used space down to an insignificant amount. Hi Eric, sorry, I had overlooked that the second screenshot was taken while scanning as root. Out of interest, how did you do this? The way I suggested, or did you find a different way? I would like to update the help documentation accordingly. Your assumption about miscelleneous space is correct. However, none of this explains why this is 565 GB in your case, as you did scan from the root folder, did not apply a filter, used physical file size as measure, and the low-level file system data should never be this much. Maybe this is due to a low-level failure somehow (e.g. due to the health of the HDD, or the low-level file system data being somehow inconsistent)? I do not think it's something GrandPerspective can help you with, I am afraid. To run as root, I first set the file size option to Physical in GrandPerspective Preferences, then ran sudo /path/to/GrandPerspective. In Terminal, when the prompt returned after a short moment, I tried several more times and then assumed it didn't work somehow. Then I tried again and started doing something else. After after some time GrandPerspective opened with the result, so I simply hadn't waited before I expected the Terminal command to "hang" until something happened before returning to the prompt. I had used this iMac with the Mac Server App at one point before giving it to my wife.
0 Comments
Leave a Reply. |