View previous topic :: View next topic |
Author |
Message |
karlika n00b
Joined: 13 Jan 2005 Posts: 8 Location: Graz/Austria
|
Posted: Mon Jul 07, 2008 12:01 pm Post subject: cifs write incredibly slow after last weeks updates [SOLVED] |
|
|
Hi,
I got two gentoo systems with different hardware, one with a 2.6.23_r3 and one 2.6.24_r8.
Both mount a share on a Windows 2003 Server for backing up some data.
Write speed was never too fast, about 2-3MB/s which is rather slow for Gigabit, but acceptable.
But now, after doing last weeks updates write speeds have fallen to 50-200KB/s!
Additionally the network device is completely blocked. Up to 90% of ping packets get lost and access by ssh is almost impossible.
The Windows server is accessible without a problem though.
I did not yet try to do a rollback of the updates and I really would like to avoid that if possible.
Did anyone have the same problem?
Regards,
Marko
Last edited by karlika on Thu Jul 17, 2008 8:21 am; edited 1 time in total |
|
Back to top |
|
|
drescherjm Advocate
Joined: 05 Jun 2004 Posts: 2790 Location: Pittsburgh, PA, USA
|
Posted: Mon Jul 07, 2008 8:18 pm Post subject: |
|
|
Quote: | Additionally the network device is completely blocked. Up to 90% of ping packets get lost and access by ssh is almost impossible. |
If you did not update your kernel this is probably a hardware problem. _________________ John
My gentoo overlay
Instructons for overlay |
|
Back to top |
|
|
karlika n00b
Joined: 13 Jan 2005 Posts: 8 Location: Graz/Austria
|
Posted: Tue Jul 08, 2008 7:39 am Post subject: |
|
|
Quote: | If you did not update your kernel this is probably a hardware problem. |
That was my first thought, but it happend on both machines after the updates and there was no kernel update included. |
|
Back to top |
|
|
karlika n00b
Joined: 13 Jan 2005 Posts: 8 Location: Graz/Austria
|
Posted: Thu Jul 17, 2008 8:23 am Post subject: Solved |
|
|
It wasn't just cifs, that was running slow...
It turned out that I had a route in my device config, that did not work any more because of a hardware change.
The connection to the Windows server should not have been affected, but it was for some unknown reason.
After removing the route everything works fine now.
Regards,
Marko |
|
Back to top |
|
|
|