-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
task txg_sync:4579 blocked for more than 120 seconds #7946
Comments
@kpande So i can safely ignore this message although it's a call trace? |
Thanks for the quick answer. Just let me understand it: So when the hdd is somehow too slow to handle that load, does the data still get completely written to disk (it just takes more time than usual) or is the call trace an evidence that not all data is written completely/correctly? thanks in advance |
@jumbi77 everything will always be written safely. The ' blocked for more than 120 seconds' warning indicates that there was a kernel thread blocked for longer than expected. The warning is advisory, and is useful for debugging/troubleshooting. It is often caused by a slow disk or oversubscribed subsystem. |
Just to clarify, I had considered writing an article on it, but I don't really have much to add to something like this, other than to add that |
System information
Describe the problem you're observing
I have a zpool with a single drive (ata-ST3000DM001) and some datasets. One dataset is used for downloading big iso and tar files. Downloadspeed is at around 25-30 mb/s, because i set copies=2 i guess the hdd has to handle about 60 mb/s of writes (which should be not to much data for the hdd). After beginning the write load (downloading) i almost always get some call traces after 1-3 minutes. If i manually limit the download speed at around 11 mb/s or set copies=1 no call traces appears. So what is causing the error? Is the hdd to slow (which i dont expect) or is it zfs related? I can reproduce the call trace and can log some other metrics if you want.
Thanks
Include any warning/errors/backtraces from the system logs
DMESG output:
ZFS GET ALL mypool/ds1:
The text was updated successfully, but these errors were encountered: