storemap 0.9
Prints the store layout, file sizes and the age of every journal, so a runaway journal is visible a week before it is a support case.
storemap --store . --depth 2 --sizesNote from the shelf row: A journal older than 24 h is the first thing to look at.
Before you install
- Runs on: Windows, Linux, macOS. the application must be 4.0.7 to 4.1.6.
- Space: about 64 KB for the download, plus [WORKING SPACE] while it runs. Reads metadata only.
- Rights: an ordinary user account; no elevation and no sudo for the tool itself
- Know first: [PREREQUISITE] — whoever writes this page up properly should say here what has to be true before the tool will run at all.
Download and verify
Take the build for your platform from the [SHARE] and check it against the digest on the shelf row before you unpack anything. The digest is also printed below.
certutil -hashfile storemap-0.9-win64.zip MD5
md5sum storemap-0.9-linux-x64.tar.gz
md5 storemap-0.9-macos.tar.gzExpected: 1b88c2af09d5. The shelf row carries the same digest.
Install
Copy it into place and put it on the path. Nothing here installs a service or a scheduled task, so there is no installer to run and nothing to reboot.
Windows
Unpack the zip, then:
xcopy storemap-0.9-win64 C:\Tools\storemap /E /I
setx PATH "%PATH%;C:\Tools\storemap"
storemap --versionLinux
Unpack it and link it onto the path:
# unpack into place
sudo tar -xzf storemap-0.9-linux-x64.tar.gz -C /opt
sudo ln -sf /opt/storemap/storemap /usr/local/bin/storemap
storemap --versionmacOS
Unpack it and link it onto the path:
# unpack into place
sudo tar -xzf storemap-0.9-macos.tar.gz -C /opt
sudo ln -sf /opt/storemap/storemap /usr/local/bin/storemap
storemap --versionCheck it worked
Check the version first, then run the one command the tool exists for. If the output matches, it is working:
storemap --version
storemap --store . --depth 2 --sizesExpected output is the line shown in the block above; anything else means [TO DO: write the failure list].
Removing it
Delete the folder and drop the path entry. The tool keeps no state of its own, so there is nothing to unregister.
rmdir /s /q C:\Tools\storemap
sudo rm -rf /opt/storemap /usr/local/bin/storemap
sudo rm -rf /opt/storemap /usr/local/bin/storemapIf it goes wrong
- [KNOWN FAILURE 1] — the usual fixes for this tool have not been written down yet. Add them the second time somebody hits one.
- Wrong error number or a fault you cannot name: run the tool's own diagnostic first (shelf row), then the removal steps.
- Before any repair that writes to a store, take the export — backoff is the tool for it.
- If a tool on this shelf is being asked to fix something it was never written for, stop and ask the desk rather than reaching for a force flag.