Re: possible bus loading problem during resync

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




If that is true, how does that happen, the driver is hung? But anyway,
how can such things happen when there is more than one CPU-core?

A drive produces an error, the whole controler hangs and resets all
ports, all drives have to finish being reset before any IO can continue.
Hapens easily enough.
Ok but this is a multi-core CPU and he said Putty and WinSCP were hung.
Ok for WinSCP... but Putty?

Timothy is Putty hung on array check even on NCQ disabled?

What is the resync speed? If it is very high it could be a CPU starvation but it's strange with only 2 drives. If it is very low I am not sure.
Are disks write caches enabled?

I am not able to spot any problem from your iostat or dmesg.
Note: yes the iostat -x 1 was supposed to be captured during resync.
Trigger a resync manually for the test. You can start it with echo check and stop it with echo idle > /sys/block/mdX/md/sync_action


--
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

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux