anyone running with large server parms on linux afs servers?

[Nathan Neulinger]

Russ Allbery wrote:
> 
> Neulinger, Nathan <nneul@umr.edu> writes:
> 
> > We're running with these
> 
> > Instance fs, (type is fs) currently running normally.
> >     Auxiliary status is: file server running.
> >     Process last started at Mon Apr 30 12:59:20 2001 (4 proc starts)
> >     Last exit at Mon Apr 30 12:59:20 2001
> >     Last error exit at Mon Apr 30 12:59:20 2001, by vol, due to signal 11
> >     Command 1 is '/usr/afs/bin/fileserver -implicit rl -L -p 24 -rxpck 800
> > -udpsize 2048000'
> >     Command 2 is '/usr/afs/bin/volserver -p 16 -udpsize 2048000'
> >     Command 3 is '/usr/afs/bin/salvager'
> 
> > recently over the past couple weeks we've started seeing volserver
> > issues (unpredictable) when moving volumes. there has been some
> > discussion here that it might be related to the large params.
> 
> Just as a data point for what it's worth (we're on Solaris rather than
> Linux), we've been running with these parameters since pretty much the
> beginning of time:
> 
> Instance fs, (type is fs) currently running normally.
>     Auxiliary status is: file server running.
>     Process last started at Sat Mar 17 02:56:47 2001 (5 proc starts)
>     Last exit at Sat Mar 17 02:56:47 2001
>     Command 1 is '/usr/afs/bin/fileserver -nojumbo -L -p 16 -rxpck 400'
>     Command 2 is '/usr/afs/bin/volserver -nojumbo'
>     Command 3 is '/usr/afs/bin/salvager'

Why the -nojumbo? Do you actually have routers that couldn't handle it,
or some other reason?

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
CIS - Systems Programming                Fax: (573) 341-4216