[OpenAFS] Problems configuring the top level of the AFS files pace

Woodman, Joel woodman@chuma1.cas.usf.edu
Mon, 3 Mar 2003 15:13:11 -0500


Derek,

> -----Original Message-----
> From: Derek Atkins [mailto:warlord@MIT.EDU]
> Sent: Monday, March 03, 2003 1:41 PM
> To: Woodman, Joel
> Cc: 'openafs-info@openafs.org'
> Subject: Re: [OpenAFS] Problems configuring the top level of the AFS
> filespace

> You needed to have the server up before you can start the client..
> It's a chicken-and-egg type of problem.  Or, if you use -dynroot,
> then root.afs (or indeed /afs) is never an AFS volume.

Here's a list of active AFS-related processes on the server:

root       634  0.0  1.2  4052 3092 ?        S    11:17   0:00
/usr/afs/bin/bosserver
root       643  0.0  0.0     0    0 ?        SW   11:17   0:00
[afs_rxlistener]
root       644  0.0  1.4  5164 3776 ?        S    11:17   0:00
/usr/afs/bin/buserver
root       649  0.0  0.0     0    0 ?        SW   11:17   0:00
[afs_callback]
root       650  0.0  1.7  5636 4532 ?        S    11:17   0:00
/usr/afs/bin/ptserver
root       651  0.0  2.3  7472 5952 ?        S    11:17   0:00
/usr/afs/bin/vlserver
root       652  0.0  2.1  6436 5392 ?        S    11:17   0:00
/usr/afs/bin/kaserver
root       654  0.0  0.0     0    0 ?        SW   11:17   0:00 [afs_rxevent]
root       655  0.0  1.8 38840 4712 ?        S<   11:17   0:00
/usr/afs/bin/fileserver
root       656  0.0  1.5  5116 3952 ?        S    11:17   0:00
/usr/afs/bin/volserver
root       657  0.0  0.5  2336 1300 ?        S    11:17   0:00
/usr/afs/bin/upserver -crypt /usr/afs/etc -clear /usr/a
root       659  0.0  0.0     0    0 ?        SW   11:17   0:00 [afsd]
root       660  0.0  0.0     0    0 ?        SW   11:17   0:00
[afs_checkserver]
root       665  0.0  0.0     0    0 ?        SW   11:17   0:00
[afs_background]
root       666  0.0  0.0     0    0 ?        SW   11:17   0:00
[afs_background]
root       667  0.0  0.0     0    0 ?        SW   11:17   0:00
[afs_background]
root       668  0.0  0.0     0    0 ?        SW   11:17   0:00
[afs_background]
root       669  0.0  0.0     0    0 ?        SW   11:17   0:00
[afs_background]

-dynroot wasn't referenced in "Installing the First AFS Machine" in the
docs, so I didn't use it as a flag, anywhere. Assuming the RedHat RPMs
install this, how would I then see and interact with AFS volumes on the
system?

Here's the AFS section of the recent boot log:

Mar  3 11:17:48 XXXXXXXX kernel: Starting AFS cache scan...------------[ cut
here ]------------
Mar  3 11:17:48 XXXXXXXX kernel: kernel BUG at vmalloc.c:253!
Mar  3 11:17:48 XXXXXXXX kernel: invalid operand: 0000
Mar  3 11:17:48 XXXXXXXX kernel: libafs-2.4.18-24.8.0 autofs 3c59x
iptable_filter ip_tables mousedev keybdev hid inpu
t usb-uhci usbcore ext3 jbd  
Mar  3 11:17:48 XXXXXXXX kernel: CPU:    0
Mar  3 11:17:48 XXXXXXXX kernel: EIP:    0010:[<c012d0ed>]    Tainted: PF
Mar  3 11:17:48 XXXXXXXX kernel: EFLAGS: 00010202
Mar  3 11:17:48 XXXXXXXX kernel: 
Mar  3 11:17:48 XXXXXXXX kernel: EIP is at __vmalloc [kernel] 0x25
(2.4.18-24.8.0)
Mar  3 11:17:48 XXXXXXXX kernel: eax: 000fffa9   ebx: fffa9000   ecx:
00000035   edx: fffa81c0
Mar  3 11:17:48 XXXXXXXX kernel: esi: 00030d40   edi: 0000000a   ebp:
fffa81c0   esp: ce129b7c
Mar  3 11:17:48 XXXXXXXX kernel: ds: 0018   es: 0018   ss: 0018
Mar  3 11:17:48 XXXXXXXX kernel: Process afsd (pid: 637, stackpage=ce129000)
Mar  3 11:17:48 XXXXXXXX kernel: Stack: fffa81c0 fffa81c0 00030d40 0000000a
fffa81c0 d08ecb9b fffa81c0 000001f2 
Mar  3 11:17:48 XXXXXXXX kernel:        00000163 fffa81c0 d0921000 0000b5cd
d09270d8 fffa81c0 00030d40 d0caf350 
Mar  3 11:17:48 XXXXXXXX kernel:        0000c350 d08ece44 fffa81c0 00000001
d09270d8 d09270d8 000106a8 fffa81c0 
Mar  3 11:17:48 XXXXXXXX kernel: Call Trace: [<d08ecb9b>] linux_alloc
[libafs-2.4.18-24.8.0] 0xab (0xce129b90))
Mar  3 11:17:48 XXXXXXXX kernel: [<d08ece44>] osi_linux_alloc
[libafs-2.4.18-24.8.0] 0x14 (0xce129bc0))
Mar  3 11:17:48 XXXXXXXX kernel: [<d08b8432>] afs_osi_Alloc
[libafs-2.4.18-24.8.0] 0x42 (0xce129be0))
Mar  3 11:17:49 XXXXXXXX kernel: [<d08b405c>] afs_dcacheInit
[libafs-2.4.18-24.8.0] 0x23c (0xce129bf8))
Mar  3 11:17:49 XXXXXXXX kernel: [<d08b40d1>] afs_dcacheInit
[libafs-2.4.18-24.8.0] 0x2b1 (0xce129c00))
Mar  3 11:17:49 XXXXXXXX kernel: [<d08b3ffc>] afs_dcacheInit
[libafs-2.4.18-24.8.0] 0x1dc (0xce129c08))
Mar  3 11:17:49 XXXXXXXX kernel: [<d08c4490>] afs_vcacheInit
[libafs-2.4.18-24.8.0] 0x50 (0xce129c18))
Mar  3 11:17:49 XXXXXXXX kernel: [<d08b6022>] afs_CacheInit
[libafs-2.4.18-24.8.0] 0x152 (0xce129c30))
Mar  3 11:17:49 XXXXXXXX kernel: [<d08f20fa>] afs_syscall_call
[libafs-2.4.18-24.8.0] 0x66a (0xce129c70))
Mar  3 11:17:49 XXXXXXXX kernel: [<d0913c64>] afs_iclLongTermSetp
[libafs-2.4.18-24.8.0] 0x0 (0xce129ca0))
Mar  3 11:17:49 XXXXXXXX kernel: [<c02200b0>] clear_user [kernel] 0x4c
(0xce129cbc))
Mar  3 11:17:49 XXXXXXXX kernel: [<c0150b0f>] load_elf_binary [kernel] 0x4cf
(0xce129cdc))
Mar  3 11:17:49 XXXXXXXX kernel: [<c013866c>] getblk [kernel] 0x18
(0xce129d0c))
Mar  3 11:17:49 XXXXXXXX kernel: [<c019f822>] ide_build_sglist [kernel] 0x8e
(0xce129d1c))
Mar  3 11:17:49 XXXXXXXX kernel: [<d081d90a>] ext3_get_block_handle [ext3]
0x52 (0xce129d38))
Mar  3 11:17:49 XXXXXXXX kernel: [<c01151ac>] __wake_up [kernel] 0x44
(0xce129d84))
Mar  3 11:17:49 XXXXXXXX kernel: [<c01151ac>] __wake_up [kernel] 0x44
(0xce129dac))
Mar  3 11:17:49 XXXXXXXX kernel: [<c0188fc3>] locate_hd_struct [kernel] 0x27
(0xce129db4))
Mar  3 11:17:49 XXXXXXXX kernel: [<c01890a6>] account_io_end [kernel] 0x22
(0xce129dc4))
Mar  3 11:17:49 XXXXXXXX kernel: [<c018914f>] req_finished_io [kernel] 0x37
(0xce129dd0))
Mar  3 11:17:49 XXXXXXXX kernel: [<c01735eb>] scrup [kernel] 0xf7
(0xce129dec))
Mar  3 11:17:49 XXXXXXXX kernel: [<c0194561>] ide_do_request [kernel] 0x2d
(0xce129e04))
Mar  3 11:17:49 XXXXXXXX kernel: [<c01735eb>] scrup [kernel] 0xf7
(0xce129e28))
Mar  3 11:17:49 XXXXXXXX kernel: [<c0174a7a>] lf [kernel] 0x4e (0xce129e5c))
Mar  3 11:17:49 XXXXXXXX kernel: [<c0176913>] do_con_write [kernel] 0x137
(0xce129e94))
Mar  3 11:17:49 XXXXXXXX kernel: [<c01b5c19>] vgacon_cursor [kernel] 0xa9
(0xce129ee0))
Mar  3 11:17:49 XXXXXXXX kernel: [<c017403d>] set_cursor [kernel] 0x61
(0xce129ef8))
Mar  3 11:17:49 XXXXXXXX kernel: [<c016b902>] write_chan [kernel] 0x156
(0xce129f18))
Mar  3 11:17:49 XXXXXXXX kernel: [<d08f25bf>] afs_syscall
[libafs-2.4.18-24.8.0] 0x18f (0xce129f40))
Mar  3 11:17:49 XXXXXXXX kernel: [<c0167efc>] tty_write [kernel] 0xc0
(0xce129f7c))
Mar  3 11:17:49 XXXXXXXX kernel: [<c016b7ac>] write_chan [kernel] 0x0
(0xce129f80))
Mar  3 11:17:49 XXXXXXXX kernel: [<c010896b>] system_call [kernel] 0x33
(0xce129fc0))

My /etc/pam.d/login is as follows:

#%PAM-1.0
auth       required     /lib/security/pam_securetty.so
auth       required     /lib/security/pam_stack.so service=system-auth
auth       required     /lib/security/pam_nologin.so
auth       sufficient   /lib/security/pam_afs.so try_first_pass ignore_root
account    required     /lib/security/pam_stack.so service=system-auth
password   required     /lib/security/pam_stack.so service=system-auth
session    required     /lib/security/pam_stack.so service=system-auth
session    optional     /lib/security/pam_console.so

> Right.  Remove the runntp service.  You neither need it nor want it.
> But that's a different issue.

Okay. That's straightforward enough to fix.
 
> > For the record, this is a RedHat 8.0 system, running the 
> 2.4.18-24.8.0
> > kernel and OpenAFS 1.2.8. It is intended to be the first 
> system in the cell.
> 
> Did you rebuild the kernel module?  2.4.18-24.8.0 is not one of the
> pre-built modules.

That was the first problem I ran into, and yes, I rebuilt the kernel module.
libafs-2.4.18-24.8.0.o is in /usr/vice/etc/modload.

> -derek
> 
> -- 
>        Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>        Member, MIT Student Information Processing Board  (SIPB)
>        URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
>        warlord@MIT.EDU                        PGP key available
> 

-Joel