I assume, that there is no physical error on the harddisks, because nothing shows up in log files, SMART values are OK, resync end with no error and fsck also found nothing to repair. So I changed the scheduler from cfq to deadline, but this only takes a couple of minutes longer until the RAID locks up. In iotop, I can see the process "smbd", which I used for the file transfer - it uses about 98% of IO. Trying to unmount or stop the array will take forever, even if I try to kill the smbd process. I will now try to get a lock by transferring a file to a harddisk which is not in this array. -Alex 2012/7/16 Alexander Schleifer <alexander.schleifer@xxxxxxxxxxxxxx>: > Hi, > > after re-sync and fsck, everything seems fine. The first try to copy a > big test file to the raid5 starts with a speed of ~45 MB/s which is > perfect, but after a couple of minutes the speed goes down to ~10 > KB/s. The only way to get the raid5 working again was to reset the > system. The raid5 then goes again in resync from an unclean array. I > checked dmesg, but found nothing. What can I do to get more > information what is going on there? > > Thanks, > Alex -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
