Re: ncpfs: Connection invalid / Input-/Output Errors

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

 



Hi,

thanks for your answere.

Anton Altaparmakov schrieb:
> Are you using IPX or TCP/IP or UDP?  Are you using the same on both?

Sorry missed pointing that out. We are using IPX. I don't think it'll
be that easy to switch to anything other :/

> Are the two boxes in the same place and on the same connection/the same
> speed?  For example if one box is sitting close to the netware server
> and the other further away, on a congested network, it is much more
> likely to loose the connection.  

Both systems are local and therefore thats not the difference,
between them.

> Also IPX is much worse than UDP.  Our connection loss
> problems decreased a lot when we moved from IPX to UDP.
> Haven't had much experience with TCP/IP yet.  Also so far we have not
> seen any connection loss problems since we switched from 2.4 to 2.6
> kernels (suse 9.3, i.e. 2.6.11.4-21.9).

Well i can imagine that IPX is much worse than UDP ("IPX just sucks").
Unfortunately it doesn't seem to be that easy to switch that system
over to UDP, cause the Novell Server is in center of a whole system,
which has to be highly available, so we don't want to touch it.

> One of the reasons for a connection disappearing is that the NCP
> sequence numbers on the netware server and the linux client become out
> of sync.  When the netware server detects this it shuts down the
> connetion.  Linux can't do reconnects so you get exactly the errors you
> see and the connection is gone.  The fix is to umount and to mount again
> when this happens.

Uhmm... then remains the question: Why should that happen on the first
machine but not on the second?


> To see if this is your problem, insert some printk()s in the relevant
> ncpfs code (depends whether you are using ipx or tcp/udp as to where)

Well - i'm using IPX. So where do i insert the printk()s? And what kind
of printk()s should i insert? Please don't think of me as an idiot,
but i'm just not firm with "kernel hacking".

> Hope this is useful.

A little bit. Thanks anywaysw

Greets
Patrick
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]
  Powered by Linux