Disk

A sysops toolkit for scanning, monitoring, reporting, alerting, tracking usage, checking health, fixing issues, cleaning up, backing up, restoring, logging, benchmarking, and comparing disk-related operations — all from the command line with full history tracking.

Commands

Each data command (scan, monitor, report, etc.) works in two modes:

• With arguments: Logs the input with a timestamp and saves to the corresponding .log file
• Without arguments: Displays the 20 most recent entries from that command's log

Data Storage

All data is stored locally in ~/.local/share/disk/. Each command writes to its own log file (e.g., scan.log, monitor.log, cleanup.log). A unified history.log tracks all activity across commands with timestamps.

• Log format: YYYY-MM-DD HH:MM|<input>
• History format: MM-DD HH:MM <command>: <input>
• No external database or network access required
• Set DISK_DIR environment variable to change data directory (default: ~/.local/share/disk/)

Requirements

• Bash 4+ (uses set -euo pipefail)
• Standard POSIX utilities: date, wc, du, head, tail, grep, basename, cat
• No root privileges needed
• No API keys or external dependencies

When to Use

1. Tracking disk usage over time — Use disk usage and disk monitor to log periodic disk space readings, building a historical record you can search and export later
2. Recording cleanup and maintenance actions — Use disk cleanup and disk fix to keep a timestamped log of what was cleaned, freed, or repaired on which servers
3. Documenting backup and restore operations — Use disk backup and disk restore to maintain an audit trail of when backups were made and restores performed
4. Benchmarking and comparing disk performance — Use disk benchmark and disk compare to log I/O test results across different drives or configurations
5. Generating exportable reports — Use disk export json to produce a structured file of all logged activity for capacity planning, compliance, or team handoff

Examples

Log a disk scan and review history

# Record a scan result
disk scan "/dev/sda1: 78% used, 45GB free"

# View recent scan entries
disk scan

Monitor and alert workflow

# Log a monitoring observation
disk monitor "Server-01 /var at 92% — approaching threshold"

# Log an alert
disk alert "CRITICAL: /data partition at 98% on prod-db-03"

# Search for all entries mentioning a server
disk search "prod-db-03"

Cleanup and fix tracking

# Log a cleanup action
disk cleanup "Removed 12GB of old Docker images on build-server"

# Log a fix
disk fix "Extended /var/log LVM volume by 10GB"

# View recent activity
disk recent

Export and statistics

# Summary stats across all log files
disk stats

# Export everything as JSON
disk export json

# Export as CSV for spreadsheet analysis
disk export csv

# Health check
disk status

Backup and restore documentation

# Log a backup
disk backup "Full backup of /home to s3://backups/2025-03-18"

# Log a restore
disk restore "Restored /etc/nginx from backup-2025-03-15.tar.gz"

# Log a benchmark
disk benchmark "fio sequential read: 520 MB/s on /dev/nvme0n1"

How It Works

Disk uses a simple case-dispatch architecture in a single Bash script. Each command maps to a log file under ~/.local/share/disk/. When called with arguments, the input is appended with a timestamp. When called without arguments, the last 20 lines of that log are displayed. The stats command aggregates counts across all logs, export serializes everything into your chosen format, and search greps across all log files for a given term.

Support

• Website: bytesagain.com
• Feedback: bytesagain.com/feedback
• Email: hello@bytesagain.com

Powered by BytesAgain | bytesagain.com | hello@bytesagain.com