[OpenAFS] Fileserver in semi-meltdown state

[Renata Maria Dart]

Thanks for your response Jeffrey.  So, if I want to try the limit
method, would the recommended procedure be to change the init 
script to read:

if [ -x /usr/afs/bin/bosserver ]; then
        ulimit -H -n 1024
        echo "Starting AFS Server processes"
        /usr/afs/bin/bosserver &
        OPTIONS="$OPTIONS -nosettime"
        sleep 30
fi

This would affect more than the fileserver.

Thanks,

Renata

>Delivered-To: openafs-info-assassin@rt.central.org
>Delivered-To: openafs-info@openafs.org
>From: Jeffrey Hutzelman <jhutz@cmu.edu>
>To: Renata Maria Dart <renata@slac.stanford.edu>, openafs-info@openafs.org
>MIME-Version: 1.0
>Content-Disposition: inline
>Subject: Re: [OpenAFS] Fileserver in semi-meltdown state
>Content-Transfer-Encoding: 7bit
>X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on illinois.central.org
>X-Spam-Level: 
>X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=ham version=2.63
>X-SA-Exim-Version: 4.0 (built Sat, 24 Apr 2004 12:31:30 +0200)
>X-BeenThere: openafs-info@openafs.org
>X-Mailman-Version: 2.0.4
>List-Help: <mailto:openafs-info-request@openafs.org?subject=help>
>List-Post: <mailto:openafs-info@openafs.org>
>List-Subscribe: <https://lists.openafs.org/mailman/listinfo/openafs-info>, 
<mailto:openafs-info-request@openafs.org?subject=subscribe>
>List-Id: OpenAFS Info/Discussion <openafs-info.openafs.org>
>List-Unsubscribe: <https://lists.openafs.org/mailman/listinfo/openafs-info>, 
<mailto:openafs-info-request@openafs.org?subject=unsubscribe>
>List-Archive: <https://lists.openafs.org/pipermail/openafs-info/>
>Date: Thu, 22 Jul 2004 20:57:05 -0400
>X-PMX-Version: 4.6.0.99824, Antispam-Core: 4.6.1.104326, Antispam-Data: 
2004.7.22.108354
>
>
>
>On Tuesday, July 20, 2004 09:27:44 -0700 Renata Maria Dart 
><renata@slac.stanford.edu> wrote:
>
>> Hi, I am currently experiencing slow or non-existent response time
>> from one of our fileservers, running OpenAFS 1.2.11 on solaris 9.
>> Vos commands hang and an ls of directories on that server also hangs.
>
>So, I don't know if this is the cause of your current problem, but there is 
>a known problem you will run into sooner or later on Solaris 9 which will 
>cause the fssync interface to become non-responsive.  The symptoms are that 
>volume operations requiring attaching volumes, including dump, move, 
>release, and single-volume salvages, all will hang.
>
>The fix is to apply the patch in DELTA rx-lwp-fdsetsize-20040708
>Alternately, you can work around the problem by insuring that the 
>fileserver is run with a _hard_ file descriptor limit of no more than 1024.
>
>-- Jeffrey T. Hutzelman (N3NHS) <jhutz+@cmu.edu>
>   Sr. Research Systems Programmer
>   School of Computer Science - Research Computing Facility
>   Carnegie Mellon University - Pittsburgh, PA
>
>_______________________________________________
>OpenAFS-info mailing list
>OpenAFS-info@openafs.org
>https://lists.openafs.org/mailman/listinfo/openafs-info

 Renata Dart                         | renata@SLAC.Stanford.edu  
 Stanford Linear Accelerator Center  |    
 2575 Sand Hill Road, MS 97          | (650) 926-2848 (office)
 Stanford, California   94025        | (650) 926-3329 (fax)