Hello Maximilian Thanks for your answer
> you should start by posting the error messages and an > vmstat 1 run when that happens. VMstat shows the following: procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu---- r b swpd free buff cache si so bi bo in cs us sy id wa 0 0 0 786736 8900 123768 0 0 581 57 181 370 4 3 83 10 0 0 0 786736 8900 123768 0 0 0 0 270 249 0 0 100 0 1 0 0 786736 8900 123768 0 0 0 0 290 253 0 14 86 0 0 0 0 786688 8900 123904 0 0 0 0 339 240 1 2 97 0 0 0 0 786424 8900 123904 0 0 0 0 328 461 2 0 98 0 8 0 0 786424 8908 123896 0 0 0 108 549 835 0 2 98 0 0 0 0 786424 8908 123896 0 0 0 0 461 831 0 0 100 0 0 0 0 786424 8908 123896 0 0 0 0 447 417 0 0 100 0 0 1 0 783516 8948 125352 0 0 1316 0 458 1566 2 2 70 26 0 1 0 783516 8948 125352 0 0 0 0 372 342 0 0 50 50 0 1 0 783516 8956 125344 0 0 0 300 333 216 0 0 50 50 0 1 0 783516 8956 125344 0 0 0 0 332 159 0 0 50 50 0 1 0 783516 8956 125344 0 0 0 0 313 147 0 0 50 50 0 1 0 783516 8956 125344 0 0 0 20 344 172 0 0 50 50 0 1 0 783424 8956 125344 0 0 0 0 316 392 1 0 50 49 0 1 0 783424 8964 125336 0 0 0 60 361 400 0 0 50 51 0 1 0 783424 8964 125336 0 0 0 0 313 140 0 2 50 48 0 1 0 783424 8964 125336 0 0 0 0 329 146 0 0 50 50 0 1 0 783440 8964 125336 0 0 0 340 449 213 0 0 50 50 0 1 0 783440 8964 125336 0 0 0 0 316 285 1 8 50 42 0 1 0 783440 8976 125392 0 0 4 40 273 171 0 0 50 50 0 1 0 783440 8976 125392 0 0 0 0 270 161 0 0 50 50 0 1 0 783440 8976 125392 0 0 0 0 252 152 0 0 50 50 0 1 0 783440 8976 125392 0 0 0 0 269 167 0 0 50 50 0 1 0 783456 8976 125392 0 0 0 0 252 209 0 0 50 50 0 1 0 783456 8984 125384 0 0 0 40 287 182 0 0 50 50 The point, where idle and wait got to 50 50 is where i started Thunderbid and nfs started to hang Messages in /var/log/messages Sep 24 13:28:17 rincewind kernel: nfs: server ponder not responding, still trying Sep 24 13:41:45 rincewind kernel: nfs: server ponder not responding, still trying NFSStat infos: Client packet stats: packets udp tcp tcpconn 0 0 0 0 Client rpc stats: calls retrans authrefrsh 1295 16 0 Client nfs v3: null getattr setattr lookup access readlink 0 0% 560 43% 25 1% 314 24% 201 15% 0 0% read write create mkdir symlink mknod 83 6% 21 1% 7 0% 0 0% 1 0% 0 0% remove rmdir rename link readdir readdirplus 6 0% 0 0% 3 0% 1 0% 0 0% 63 4% fsstat fsinfo pathconf commit 0 0% 4 0% 0 0% 2 0% Client nfs v4: null read write commit open open_conf 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% open_noat open_dgrd close setattr fsinfo renew 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% setclntid confirm lock lockt locku access 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% getattr lookup lookup_root remove rename link 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% symlink create pathconf statfs readlink readdir 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% server_caps delegreturn 0 0% 0 0% Let me know If you like to have more information from rpcdebug or somthing else. > but today 2.6.18 came out so better check if that one works for you, Is not an option yet. I will test, when 2.6.18 is in unstable. > instructions where to find the trunk images: > http://wiki.debian.org/DebianKernel Regards Matthias Kreis -- remasec kreis Matthias Kreis E-Mail: [EMAIL PROTECTED] Alte Landstrasse 106 Tel: 071 770 0350 Postfach 202 Fax: 071 770 0351 9445 Rebstein Web: www.remasec.ch -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
