I'm running 2.1.35 on two machines in two different environments.
The first is my home system, connected to the Net via a 33.6k serial modem.
The sedond is my work machine which is in an NFS/NIS/AMD enviroment that I
have implemented, on 100Mb. Both systems are using:
2.1.35, mount-2.6e, modules-2.1.34, libc-5.4.23 and other necessary goodies
listed in Documentation/Changes. **
** The one exception is that I can't get linux-nfs-0.4.21 to compile at
work; I sent a report to Olaf already.
Here are the problems I'm seeing common to both:
1.) There are constant outbursts of arp error messages, usually coninciding
with network load (makes sense). They look like this:
Apr 16 11:51:27 terror kernel: arp_free called from SPL=0
Apr 16 11:51:27 terror kernel: arp_purge_send_q called from SPL=0
Apr 16 11:51:27 terror kernel: arp_neigh_destroy called from SPL=0
Apr 16 11:51:27 terror kernel: arp_purge_send_q called from SPL=0
Apr 16 11:51:27 terror kernel: arp_free called from SPL=0
Apr 16 11:51:27 terror kernel: arp_purge_send_q called from SPL=0
Apr 16 11:51:27 terror kernel: arp_neigh_destroy called from SPL=0
Apr 16 11:51:27 terror kernel: arp_purge_send_q called from SPL=0
Apr 16 11:51:28 terror kernel: arp_free called from SPL=0
2.) When I make accesses to an ISO9660 filesystem, I see the following
error messages (for both CD-ROMS and loopback mounted files):
Apr 16 11:55:23 terror last message repeated 23 times
Apr 16 11:55:23 terror kernel: _isofs_bmap: block>= EOF(6, 12288)
Apr 16 11:55:23 terror kernel: _isofs_bmap: block>= EOF(6, 12288)
Apr 16 11:55:23 terror kernel: _isofs_bmap: block>= EOF(4, 8192)
Apr 16 11:55:23 terror last message repeated 3 times
Apr 16 11:55:23 terror kernel: _isofs_bmap: block>= EOF(8, 16384)
Apr 16 11:55:23 terror kernel: _isofs_bmap: block>= EOF(8, 16384)
Apr 16 11:55:23 terror kernel: _isofs_bmap: block>= EOF(6, 12288)
Apr 16 11:55:23 terror kernel: _isofs_bmap: block>= EOF(6, 12288)
Apr 16 11:55:24 terror kernel: _isofs_bmap: block>= EOF(18, 36864)
Problems that I see that only pertain to the work computer:
Apr 16 12:01:50 terror kernel: nfs warning: mount version older than kernel
As stated, I'm using mount-2.6e. I'll admit, this could be my fault because
I can't get linux-nfs-0.4.21 to compile yet, so...
Problems that I see only on the home machine:
There apparently may be a bug in path MTU discovery. I've noticed for some
time now that my masqueraded hosts can not reach www.excite.com, yet I can.
Better still, this only began around 2.1.32. I've sent tcpdumps to David
Miller and Keith Owens; they were the ones to suspect the path MTU problem.
I'm using an MTU of 512 on my ppp coGnection, which is through my office.
I'm set both ends up to use pppd-2.2.0. I have "f.BETA1" on my end, and
2.2.0f from RedHat 4.1 on the work end (which is running 2.0.29).
Thanks for any help.
-bp
-- # Systems Administrator, Seattle Software Labs, Inc # # B. James Phillippe # Network/Sys Admin Terran.ORG # # <bryan@terran.org> # http://w3.terran.org/~bryan # # Finger for PGP key # Linux Convert - circa 1.1.59 # # Systems Administrator, Seattle Software Labs, Inc #