[OpenAFS-devel] Fileserver fast start options - what effect?

[Neulinger, Nathan]

We have been running with both options for a while.

Don't forget to add the "-DontSalvage" option to the salvager line in
BosConfig.=20

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
UMR Information Technology             Fax: (573) 341-4216


> -----Original Message-----
> From: Hartmut Reuter [mailto:reuter@rzg.mpg.de]=20
> Sent: Monday, June 30, 2003 7:59 AM
> To: Harald Barth
> Cc: openafs-devel@openafs.org
> Subject: Re: [OpenAFS-devel] Fileserver fast start options -=20
> what effect?
>=20
>=20
> Hello Harald,
>=20
> these were my additions. They do the following:
>=20
> --enable-fast-restart
>=20
> lets the salvager exit immediately whenever it is called without=20
> arguments as happens after a chrash. The fileserver had to be=20
> modified=20
> to allow attachment of volumes in state V_inUse (actually these lines=20
> are in volume.c). I made this change because also at our site the=20
> salvager took very long to end up with only having updated the=20
> uniquifier in the volinfo-file which seem not to be worth=20
> such an delay.
>=20
> Of course you can still salvage by "bos salvage server=20
> partition volume"=20
> or by "bos salvage server partition" or even by "bos salvage server=20
> -all". For NAMEI-fileservers salvaging single volumes is really fast=20
> because all data belonging to the volume group are uder a single=20
> directory. Therefore it makes sense to run a script to salvage each=20
> RW-volume one after the other instead of salvaging the=20
> partition because=20
> the fileserver has not to be stopped.
>=20
> --enable-bitmap-later
>=20
> could be enabled always. It reads the vnode-files to create=20
> the bitmap=20
> only when the 1st time a new vnode is going to be allocated.=20
> This makes=20
> the startup of the fileserver a little faster. I can't see any=20
> disadvantage of this option.
>=20
> Both options are based on code I developed for our MR-AFS=20
> fileservers.=20
> Because we do not run any OpenAFS fileserver this code could not be=20
> tested extensively in OpenAFS by our site, but I heard theat=20
> other sites=20
> are running fileservers with these options.
>=20
> Hartmut
>=20
> Harald Barth schrieb:
> > Lastest salvage took far too long (hours), and I stumbled over the
> > options --enable-bitmap-later and --enable-fast-restart. As=20
> it was not
> > very difficult to build the server by writing the options, I would
> > appreciate more information from the author(s) what these=20
> actuallu do
> > and don't do and if there is any more configuration required at
> > startup. The amount of information found by for example google
> > (search: enable-fast-restart) is astonishing low. Then I have some
> > questions to folks actually using this (I hope there are): When _do_
> > you run salvage? How do you detect volumes that are Off-line? What
> > options do you use at fileserver startup? Of course, other
> > observations, tricks concerning fast fileserver startup are welcome,
> > too.
> >=20
> > Thanks,
> > Harald.
> >=20
> > _______________________________________________
> > OpenAFS-devel mailing list
> > OpenAFS-devel@openafs.org
> > https://lists.openafs.org/mailman/listinfo/openafs-devel
>=20
>=20
> --=20
> -----------------------------------------------------------------
> Hartmut Reuter                           e-mail reuter@rzg.mpg.de
> 					   phone +49-89-3299-1328
> RZG (Rechenzentrum Garching)               fax   +49-89-3299-1301
> Computing Center of the Max-Planck-Gesellschaft (MPG) and the
> Institut fuer Plasmaphysik (IPP)
> -----------------------------------------------------------------
>=20
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>=20