[OpenAFS] linux kernel options ?

[Horst Birthelmer]

On Nov 25, 2004, at 3:59 PM, EC wrote:

>> On Nov 25, 2004, at 12:09 PM, EC wrote:
>>>>>
>>>>> OK. BTW : machine has 400MB physical RAM, 1GB SWAP, 170MB physical
>>>>> mem
>>>>> free.
>>>>> AFS cache is supposed to be ~100MB.
>>>>>
>>>>> Here's the log with -verbose -debug :
>>>>>
>>>>> Starting AFS services.....
>>>>> afsd: My home cell is 'localdomain.com'
>>>>> ParseCacheInfoFile: Opening cache info file
>>>>> '/etc/openafs/cacheinfo'...
>>>>> ParseCacheInfoFile: Cache info file successfully parsed:
>>>>>         cacheMountDir: '/srv/afs'
>>>>>         cacheBaseDir: '/var/openafs/cache'
>>>>>         cacheBlocks: 100000
>>>>> afsd: Creating '/etc/openafs/AFSLog'
>>>>> CreateCacheFile: Creating cache file '/etc/openafs/AFSLog'
>>>>> afsd: 2400 inode_for_V entries at 0x8074728, 9600 bytes
>>>>> SScall(137, 28, 17)=0 afsd: Forking rx listener daemon.
>>>>> afsd: Forking rx callback listener.
>>>>> afsd: Forking rxevent daemon.
>>>>> SScall(137, 28, 36)=0 afsd: Calling AFSOP_CACHEINIT: 2800 stat 
>>>>> cache
>>>>> entries, 2400 optimum cache files, 19660800 blocks in the cache,
>>>>> flags
>>>>> =
>>>>> 0x1, dcache entries 2400
>>>>> SScall(137, 28, 6)=0 afsd: Sweeping workstation's AFS cache
>>>>> directory.
>>>>> afsd: Using memory cache, not swept
>>>>> afsd: Calling AFSOP_CACHEINFO: dcache file is '/CacheItems'
>>>>> afsd: Calling AFSOP_CELLINFO: cell info file is '/CellItems'
>>>>> SScall(137, 28, 34)=0 SScall(137, 28, 29)=0 SScall(137, 28, 35)=0
>>>>> afsd:
>>>>> Forking AFS daemon.
>>>>> afsd: Forking Check Server Daemon.
>>>>> afsd: Forking 5 background daemons.
>>>>> afsd: Calling AFSOP_VOLUMEINFO: volume info file is '/VolumeItems'
>>>>> SScall(137, 28, 8)=2 afsd: Calling AFSOP_AFSLOG: volume info file 
>>>>> is
>>>>> '/etc/openafs/AFSLog'
>>>>> afsd: Calling AFSOP_CACHEINODE for each of the 2400 files in ''
>>>>> afsd: Calling AFSOP_GO with cacheSetTime = 0
>>>
>>
>> I think error 2 is ENOENT which means your VolumeInfo file isn't 
>> there.
>> Could you try mounting afs to /afs and use disk cache??  .... and 
>> sweep
>> that directory before. So it would be just like the first time 
>> starting
>> the client.
>> What I expect is the client creating the needed files.
>>
>> I still don't know for sure why the client stops there.
>>
>> Just another question... you do have clients working in that cell,
>> don't you??
>
> No. This is a clean machine. Out of the box Linux for a First Machine 
> AFS
> install (I rebuild it automatically with a sort of ghost)
>
> I moved to a disk cache (BTW : ext3). I get a message like
> ....
> CreateCacheFile: Creating cache file '/var/openafs/cache/D4/V9998'
> doSweepAFSCache: Creating '/var/openafs/cache/D4/V9999'
> CreateCacheFile: Creating cache file '/var/openafs/cache/D4/V9999'
> doSweepAFSCache: Closing cache directory.
> afsd: 10000 out of 10000 data cache files found in sweep 1.
> afsd: Calling AFSOP_CACHEINFO: dcache file is
> '/var/openafs/cache/CacheItems'
> /etc/rc.d/init.d/afs: line 144:   374 Segmentation fault
> $AFSDSERVER_PATH ${AFSD_OPTIONS}
>
> If I try to ksymoops but I get hundreds of warnings...

That's some sort of error from your start script. Not important right 
now.

Try to reboot the machine, do an insmod of the afs kernel module and 
start afsd by hand (just "afsd" in the shell).
When that's working you can go after your script.

Horst