-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--output FILE not in real time #6
Comments
This is actually not specific to ZFS, I get this on ext4 as well. Regular stdout is line buffered, while outputting to a file uses much larger buffers. This is more efficient especially for large amounts of data, but prevents live This is easy to fix, commit is coming. Thanks for the report! |
Thank you for your fast response.
but then I don't have line buffering. Ideally for me there should be extra '--line-buffered' option, just like in case of grep, for all outputs. Or to permit appending to existing file with '-o FILE' option. The latter would also allow for writing into created fifo. |
But now "line buffered" is the default, why would you need an extra option for that? |
still doesn't produce realtime output. In commit 06c83e0 you added After modifying code - moving line 595:
All realtime output is concatenated into $fifo. |
Hey I'm trying to use your tool to backtrack waking up disks in my ZFS pool.
When I run
and in another terminal
then immediately I get valid output in first terminal:
But when I try to redirect output to file using command
(or fatrace -c > logfile or fatrace -c | tee logfile)
and in another terminal I start
Accessing /mnt/magazyn, creating, delecting files - logfile stays empty. Only after stopping fatrace with CTRL-C all the missing content appears in the logfile.
It seems that this behavior only happens in case of ZFS mounts. Command started without "-c" saves a lot of logs into logfile in realtime, but I can't find any records from ZFS mounts.
My system: Debian 10 5.9.0-0.bpo.5-amd64
I tried fatrace from Debian Stable repository (0.13-2) and from this github. Result is the same.
The text was updated successfully, but these errors were encountered: