Subject: [netatalk-admins] Re: Sherlock takes a LONG time
From: ME (dugan@libwais.sonoma.edu)
Date: Tue Nov 23 1999 - 17:44:34 EST
The obvious tech support questions:
Between the time before when searching the netatalk volume when it was
fast, and now when it is slow:
Has any new hardware been installed on the Linux Box that is running
Netatalk?
Has there been a change in kernels being used?
Has there been a modification in network interface bindings?
Has the client had its OS upgraded, or updated with new software?
When this search is taking a long time, run "uptime" at the command prompt
no the linux box. What umbers does it report when it starts taking a long
time? Is there a heavy load on the system?
Is the hard disk on the server doing a lot of seeking (IDE, or Single CSI
Disk not HW RAID) while serving files to many users?
When fsck is run on the volume being shared, what percent of the partition
files are fragmented?
Have you included special IP filtering mechanisms for firewalls, and
packet analysis?
Did you recently uuse IP Aliasing and bing more IP addresses to any given
interface? (not ikel to case a problem)
When the Linux box is powred down, do any other machines respond to a ping
of the servers IP address?
Is there a problems with the port being used on the hub/switch?
Are you using a switched network?
Did the network administrator recently change how the switches are
configured store and forward, cut through filtering, layer3 switches etc?
If it was working quickly before, and is not searching quickly now,
*something* must have changed. What is it that has changed?
-M
*(There are more questions, but maybe one of these will start us in the
right direction.,..)
--------------------------------------------------------------------------
Systems Department Operating Systems Analyst for the Ruben Salazar Library
of California State University at Sonoma.
/UNIX(/BSD/SysV)\N_NW[.]VMS\WNTS\WNTW\W95\W311\WFWG\DOS:MacOS/NeXTSTEP
--------------------------------------------------------------------------
On Tue, 23 Nov 1999, Tom Kunz wrote:
> Subject: Sherlock takes a LONG time
>
> Everybody,
> I am having a very strange problem with a customer's netatalk
> installation. He is sharing an 8G partition, with about 2G of it used,
> from his Red Hat Linux 6.0 server to about 15 Mac's. He's using
> netatalk-1.4b2+asun2.1.3-4.i386.rpm. Saving and copying files to the
> Linux machine is as quick as ever, but when he uses Sherlock to find
> files on it, it takes an absolutely ridiculous amount of time. Up until
> the other day, Sherlock was nice and fast, equally as fast as when
> searching any other network volume. Now all of a sudden, Sherlock is
> insanely slow (up to 2 hours!) when searching this netatalk volume, but
> as fast as ever when searching non-netatalk network volumes. Afpd has
> been configured to allow up to 75 concurrent users, but that's about the
> only thing different from this and a the stock installation out of the
> rpm.
> Anybody know what is happening here? Any suggestions would be greatly
> appreciated.
> Thanks,
> Tom
>
> --
> Tom Kunz Tool Developer Software Consulting Services
> PGP Key http://www.users.fast.net/~tkunz/pgp.html
> 1452 1F99 E2BB 632E 6EAE 2DF0 EF11 4DFC
> DB62 7EBC 3BA0 6C40 88C0 C509 DA85 91B4 D5E9 EFD3
>
This archive was generated by hypermail 2b28 : Sat Dec 18 1999 - 16:17:29 EST