Christian Zimmermann writes
The result is still that I have to go there and see what is going on. Please make sure that you do not have other tasks on other machines queued to rsync or whatever with nebka for a while.
There is nothing rsyncing from nebka, afaik.
Interestingly, the rsync we did on Thursday from one disk to the other went fine.
I already wrote this is because of the e2fsck -c -y. The -c will perform a badblock san and mark all bad blocks as bad so the O/S does not go there. If you do a new scan now, you will find additional bad blocks, the o/s went there and tripped over them. I will not repeat this lecture again. Cheers, Thomas Krichel http://openlib.org/home/krichel RePEc:per:1965-06-05:thomas_krichel phone: +7 383 330 6813 skype: thomaskrichel