[OpenAFS-devel] ppc64 / 1.3.85 / 2.6.5-7.191-pseries64 - afsd problem ? / compile error

[Marco Hoehle]

I am not quiete sure if the module is loaded correctly, but i thought it is
because lsmod shows me the module as loaded and
in /proc/kallsyms i can see 2802 afs symbols loaded.
That's why i thought it succeeded....
Well but I also belive that it's something about the kernel symbol table
(Frank told me that in PPC there are 2 different tables ) - but I don't
know so much about this and that's why i have no clue about how to correct
/ fix this ...

marco




                                                                           
             Horst Birthelmer                                              
             <horst@riback.net                                             
             >                                                          To 
             Sent by:                  Marco Hoehle <MHO@zurich.ibm.com>   
             openafs-devel-adm                                          cc 
             in@openafs.org            openafs-devel@openafs.org           
                                                                   Subject 
                                       Re: [OpenAFS-devel] ppc64 / 1.3.85  
             07/15/2005 02:15          / 2.6.5-7.191-pseries64 - afsd      
             PM                        problem ? / compile error           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           





On Jul 15, 2005, at 1:45 PM, Marco Hoehle wrote:

> Building 1.3.85 on Power5 for PPC64 with SLES9 Kernel
> 2.6.5-7.191-pseries64.
>
>
> During compilation of libafs for this kernel I got the flock64
> error Frank
> already described in February.
> My workaround was just another IFDEF in src/afs/afs.h to use the
> struct
> flock instead of struct flock64.
> After this ugly patch the compilation was working and one can load the
> module.
>
> It says, that libafs cannot find the address of the system call
> table, but
> it continues anyway.
> In the earlier package provided from Sven Oehme for ppc (1.3.81 for
> 2.6.7.111.19 kernel) this behaviour was the same but it is anyway
> working.
> Also in /proc/kallsyms libafs is in, so it may work.
>
> But when loading afsd  the following errors were thrown out ....
>
> font:/opt/devel/openafs-1.3.85/src/afsd # ./afsd -memcache -verbose
> -debug
> afsd: My home cell is 'test.zurich.ibm.com'
> ParseCacheInfoFile: Opening cache info file '/usr/local/etc/openafs/
> cacheinfo'...
> ParseCacheInfoFile: Cache info file successfully parsed:
>         cacheMountDir: '/afs'
>         cacheBaseDir: '/var/cache/openafs'
>         cacheBlocks: 107618
> afsd: 13452 inode_for_V entries at 0x100487e0, 53808 bytes
> SScall(137, 28, 17)=-1 afsd: Forking rx listener daemon.
> afsd: Forking rx callback listener.
> SScall(137, 28, 48)=-1 afsd: Forking rxevent daemon.
> SScall(137, 28, 0)=-1 afsd: Forking AFSDB lookup handler.
> SScall(137, 28, 36)=-1 afsd: Error -1 in basic initialization.
> afsd: Calling AFSOP_CACHEINIT: 300 stat cache entries, 13452
> optimum cache files, 107618 blocks in the cache, flags = 0x1,
> dcache entries 13452
> SScall(137, 28, 19)=-1 SScall(137, 28, 6)=-1 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)=-1 SScall(137, 28, 29)=-1 Adding cell
> 'test.zurich.ibm.com': error -1
> SScall(137, 28, 35)=-1 afsd: Forking AFS daemon.
> afsd: Forking Check Server Daemon.
> SScall(137, 28, 1)=-1 afsd: Forking 2 background daemons.
> afsd: Calling AFSOP_VOLUMEINFO: volume info file is '/VolumeItems'
> afsd: Calling AFSOP_AFSLOG: volume info file is '/usr/local/etc/
> openafs/AFSLog'
> afsd: Calling AFSOP_CACHEINODE for each of the 13452 files in ''
> afsd: Calling AFSOP_GO with cacheSetTime = 0
> SScall(137, 28, 100)=-1 afsd: All AFS daemons started.
> afsd: Forking trunc-cache daemon.
> SScall(137, 28, 4)=-1 afsd: No check server daemon in client.
> afsd: Mounting the AFS root on '/afs', flags: 0.
> afsd: Can't mount AFS on /afs(22)
> SScall(137, 28, 2)=-1 SScall(137, 28, 2)=-1 font:/opt/devel/
> openafs-1.3.85/src/afsd # SScall(137, 28, 3)=-1
>
> The Point seems to be the :      Error -1 in basic initialization
> It does not fork the processes - only the afsd is running but
> forking nothing and waiting for a SIGKILL ...
>
>
> font:/opt/devel/openafs-1.3.85/src/afsd # ps -aef | grep afs
> root     18506     1  0 13:34 ?        00:00:00 ./afsd -memcache -
> verbose -debug
>
>
> Any Ideas - patches I missed/ forgott ??
>
> Thanks  in advance
>
> marco

Your AFS calls 17 and 19 aren't succeeding which means your module
couldn't be initialized at all. I have no idea why you're so sure
that the module is loaded correctly.
I'd say it isn't.

I suspect it has nothing to do with your patches but with the
initialization of the module and the syscall hooks.
Just speculation I can't prove.

Horst
_______________________________________________
OpenAFS-devel mailing list
OpenAFS-devel@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-devel