[DRBD-user] drbd0: [kjournald/1476] sock_sendmsg time expired, ko = 4294967295

[Sim]

> google for drbd ko-count ...
> I assume your Secondaries IO-subsystem got stuck.
>
> you should configure ko-count = 6 or so.
> it would have started to count ".... ko = 6",
> and at "ko = 0" it would have gone StandAlone,
> recovering from this situation.
>
> you should also upgrade to a 2.6 kernel,
> where this won't lock up the box but only the drbd partition.
> 2.4 has only _one_ runqueue for _all_ disks, if it gets stuck
> on one disk, all io is stuck.


Thanks for quiqly reply!

I have solved now...

A SCSI HotSwap Disk was crashed ( over HP Server ) and the system was degraded.

I'm very fun of Trustix server. Unfortunately Trustix Stable is still
2.4 kernel.

Thanks again and excuse me!

Sim