See every rsync transfer in real time with lnav

You ran rsync to mirror a directory across machines. It finished fast. No errors on the surface. But you needed to know what really happened. What files moved. What was skipped. Why some transfers took longer. And that’s when lnav stepped in.

lnav and rsync are a quiet power duo. rsync moves your data with precision. lnav lets you read the operation’s heartbeat after the fact — directly from log files, without slow pivots between tools. Pairing them means you not only transfer data but instantly see, search, and parse transfer logs like a surgeon reading charts.

With rsync’s verbose or --log-file option active, you can feed the output into lnav for immediate structured analysis. No extra pipelines. No glue scripts. lnav instantly detects timestamps, file paths, and sizes. Logs become searchable in real time. You filter for partial transfers. You pinpoint errors faster than tailing or grepping raw text.

Running large-scale file sync jobs? Stream the rsync output to a log file and launch lnav on it before the transfer is even done. Watch patterns emerge live. Check throughput trends by timestamp. Confirm cleanup steps happened. Close the gap between the transfer command and the truth of its execution.

The real strength of combining lnav with rsync is control over visibility. rsync makes no promises about easy human parsing. lnav makes no promises about moving data. Together, they give you clear windows into both movement and meaning.

To test this workflow, use a simple command:

rsync -avh --log-file=rsync.log /source/path /dest/path
lnav rsync.log

From there, you can refine. Add --itemize-changes to rsync for richer output. In lnav, toggle SQL mode for aggregated insights. Use filters to review only modified files or failed transfers from the current run.

This approach scales. Whether syncing gigabytes or terabytes, local or remote, the visibility stays instant and navigable. When operations grow complex, combining lnav and rsync reduces risk. You spend less time hunting for the why after a problem and more time fixing it.

Try the pairing now. Spin it up with your own logs or see it live in minutes with hoop.dev. Stop running blind jobs. Start seeing every transfer, every change, every result, as it happens.