-
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 mv:11533 blocked for more than 120 seconds #6265
Comments
Okay, so I've destroyed the old RAIDZ1, and made a new RAIDZ10 named
I ran bad blocks on the 4 3TB drives and they didn't seem to show any issues at all. Even performance seems okay. I assume the bad sectors got reallocated. I decided to do a backup While seeing consistently good performance:
I received several warnings:
Lots of available memory:
Load average a tad high but not too bad:
|
|
Okay, so today I coped another partition from
|
Also, after running badblocks, the drive seems to have recovered somewhat:
|
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions. |
System information
Describe the problem you're observing
This is an entirely new system with 6x 4TB WD RED drives on a SAS3 backplane with 32Gb of memory with about 12 free at the time this happened.
I have two ZFS pools:
I am copying a lot of data from the
old-tank
totank
.When copying, from
zfs iostat 5
I was getting about 250Mbytes/s READ fromold-tank
and 550Mbyte/s WRITE totank
. It was humming along quite nicely for a long time.I noticed some odd pauses and from another machine, copying via
scp
, it said "stalled" which indicates no data transfer for a few moments.Describe how to reproduce the problem
Copy lots of data. Perhaps this issue is isolated to the
old-tank
, or operations that involve it? Perhaps those drives have issues and they may not have TLER so are blocking the system?drives
iotop while mv
smartctl --all
For the four older drives, I've attached the output of smartctl. I think one of the drives may have started to go bad (wwn-0x50014ee20702e46a) - or it might have been a one off failure for some reason. I'll investigate further.
wwn-0x50014ee15a0a0c46-smart.txt
wwn-0x50014ee15a0a11ce-smart.txt
wwn-0x50014ee20702e46a-smart.txt
wwn-0x50014ee20702ef26-smart.txt
iostat
free -h
The text was updated successfully, but these errors were encountered: