-
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 blocked for more than 120 seconds on 0.6.5.3 #3952
Comments
Same problem on 14.04 LTS (Linux 3.13.0-74-generic #118-Ubuntu SMP Thu Dec 17 22:52:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux). When it happens the ZFS read operations take very long time. And it's not just txg_sync, but any process on the server accessing ZFS pool it seems.
|
I have this problem as well on a server I'm using on AWS to evaluate switching some of our data storage to ZFS. It's ZFS over EBS, which is potentially problematic as we can see. We have the same txg_sync errors as above. In addition, I've seen:
(Apologies if you got an email with another comment; that was for our internal tracking issue) |
I have the same problem on a production server:
|
are you guys all taking snapshots with cron (zfs-auto-snapshot) ? |
I was not at the time I reported this issue. |
task txg_sync blocked for more than 120 seconds
I dont know if its because of the latest ZFS release, but now my Zpools are painfully slow, Booting takes in the order of minutes. I am also seeing task "txg_sync:1625 blocked for more than 120 seconds." periodically inside dmesg and also during boot.
This is on Ubuntu 15.04. My Kernel : Linux version 3.19.0-31-generic (buildd@lcy01-07) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #36-Ubuntu SMP Wed Oct 7 15:04:02 UTC 2015
I believe this may be the same problem, or related to #3950 because I also have the issue of very very slow read speeds. This issue was not a problem before, but seems to have occurred recently (Possibly after the last upgrade of ZFS to V0.6.5.3-1).
This is the first time it happens during Boot. I have tried rebooting, and it does this all the time now.
And here it is again, happening later on. It happens regularly.
The text was updated successfully, but these errors were encountered: