[SPAM] Re: [OpenAFS] Openafs-1.6.5 client crash when update the OPTIONS in afs config file

[HUANG Qiulan]

> -----=D4=AD=CA=BC=D3=CA=BC=FE-----
> =B7=A2=BC=FE=C8=CB: "Sergio Gelato" <Sergio.Gelato@astro.su.se>
> =B7=A2=CB=CD=CA=B1=BC=E4: 2014=C4=EA12=D4=C227=C8=D5 =D0=C7=C6=DA=C1=F9
> =CA=D5=BC=FE=C8=CB: huangql <huangql@ihep.ac.cn>
> =B3=AD=CB=CD: openafs-info <openafs-info@openafs.org>
> =D6=F7=CC=E2: [SPAM] Re: [OpenAFS] Openafs-1.6.5 client crash when update=
 the OPTIONS in afs config file
>=20
> * huangql [2014-12-24 17:46:19 +0800]:
> > I failed to restart afs service after I changed OPTIONS value in /etc/s=
ysconfig/afs file.
>=20
> What was the old value, and what did you change it to?

The old value is listed as following:

CACHESIZE=3D9500000
#CACHESIZE=3D100000
OPTIONS=3D" "
#OPTIONS=3DAUTOMATIC
#OPTIONS=3D$SMALL

# you should never need to change these settings
AFSDIR=3D/afs
CACHEDIR=3D/var/cache/openafs
CACHEINFO=3D/usr/vice/etc/cacheinfo

And then I changed to new value  by setting OPTIONS and CACHESIZE as:

CACHESIZE=3D"AUTOMATIC"
OPTIONS=3D"-chunksize 19 -daemons 6 -dcache 15000 -fakestat  -files 50000 -=
stat 15000 -volumes 256"

>=20
> > At this time, I need to reboot the machine to make the new configuratio=
n validate.
>=20
> Are you saying that afsd crashes on service restart but not when it is st=
arted
> for the first time after a reboot (with the same options)?
>=20
> > Openafs version: 1.6.5
>=20
> A bit old. You may want to check the change logs of later versions for
> potentially relevant bug fixes.
>=20
> > Os version: Scientific Linux release 6.5 (Carbon)  2.6.32-431.el6.x86_6=
4=20
> >=20
> > I got the error message as following:
> >=20
> > [root@bws0609 ~]# /etc/init.d/afs restart
> > Stopping AFS client.....=20
> > Sending all processes using /afs the TERM signal ...       [  OK  ]
> > Sending all processes using /afs the KILL signal ...       [  OK  ]
> > Starting AFS client.....=20
> > /etc/init.d/afs: line 230: 26271 Segmentation fault      /usr/vice/etc/=
afsd ${AFSD_OPTIONS}
>=20
> Has a core file been left behind? If so, could you extract a backtrace fr=
om it?
>=20
> > Dec 24 17:30:29 bws0609 kernel: Starting AFS cache scan...
> > Dec 24 17:30:29 bws0609 kernel: afsd[26271]: segfault at 18 ip 00000037=
36679753 sp 00007fff5f346fa0 error 4 in libc-2.12.so[3736600000+18a000]
>=20
> To me this looks like an attempt to dereference a null pointer to a struc=
t
> (with the component of interest being at offset 0x18). A backtrace might
> help one figure out where that unexpected null pointer came from.