Re: Arla 0.42-RC2

Tomas Olsson <[email protected]> writes:

> Not good. The attached patch should fix the problem, it's also in CVS.

Applied the patch, and the ooops disappeared.

> Ok, so what happened was that arlad for some reason died before mount,
> which triggered the oops. You probably want to start arlad with
> "-n --debug=alm" or so to see what happens, or under gdb.

arlad -n --debug=alm produces the following output:

  2006-04-04 15:04:49 CEST: arla: read_conffile: /usr/arla/etc/arla.conf
  2006-04-04 15:04:49 CEST: arla: Arlad booting sequence:
  2006-04-04 15:04:49 CEST: arla: connected mode: connected
  2006-04-04 15:04:49 CEST: arla: ports_init
  2006-04-04 15:04:49 CEST: arla: uae_init
  2006-04-04 15:04:49 CEST: arla: rx
  hipri was 3 actually 0
  2006-04-04 15:04:49 CEST: arla: conn_init numconns = 100
  2006-04-04 15:04:49 CEST: arla: initconncache
  hipri was 3 actually 1
  2006-04-04 15:04:49 CEST: arla: cellcache
  2006-04-04 15:04:49 CEST: arla: poller
  2006-04-04 15:04:49 CEST: arla: initpoller
  hipri was 3 actually 1
  2006-04-04 15:04:49 CEST: arla: fprio
  2006-04-04 15:04:49 CEST: arla: volcache numvols = 100
  2006-04-04 15:04:49 CEST: arla: using rxkad level crypt
  2006-04-04 15:04:49 CEST: arla: credcache numcreds = 100
  2006-04-04 15:04:49 CEST: arla: fcache low_vnodes = 30000, high_vnodes = 40000 low_bytes = 734003200, high_bytes = 1468006400
  hipri was 3 actually 1
  hipri was 3 actually 1
  hipri was 3 actually 1
  2006-04-04 15:04:49 CEST: arla: cmcb
  2006-04-04 15:04:49 CEST: arla: cm
  2006-04-04 15:04:49 CEST: arla: arla init done.
  hipri was 3 actually 1
  hipri was 3 actually 1
  hipri was 3 actually 1
  hipri was 3 actually 1
  hipri was 3 actually 1
  hipri was 3 actually 1
  hipri was 3 actually 1
  hipri was 3 actually 1
  hipri was 3 actually 1
  hipri was 3 actually 1
  hipri was 3 actually 1
  hipri was 3 actually 1
  hipri was 3 actually 1
  hipri was 3 actually 1
  hipri was 3 actually 1
  hipri was 3 actually 1
  2006-04-04 15:04:49 CEST: arla: Arla: selecting on fd: 8
  2006-04-04 15:04:49 CEST: arla: running pinger
  2006-04-04 15:04:49 CEST: arla: poller waiting
  2006-04-04 15:04:49 CEST: arla: pre-creating nodes
  2006-04-04 15:04:49 CEST: arla: worker 0 waiting
  2006-04-04 15:04:49 CEST: arla: worker 1 waiting
  2006-04-04 15:04:49 CEST: arla: worker 2 waiting
  2006-04-04 15:04:49 CEST: arla: worker 3 waiting
  2006-04-04 15:04:49 CEST: arla: worker 4 waiting
  2006-04-04 15:04:49 CEST: arla: worker 5 waiting
  2006-04-04 15:04:49 CEST: arla: worker 6 waiting
  2006-04-04 15:04:49 CEST: arla: worker 7 waiting
  2006-04-04 15:04:49 CEST: arla: worker 8 waiting
  2006-04-04 15:04:49 CEST: arla: worker 9 waiting
  2006-04-04 15:04:49 CEST: arla: worker 10 waiting
  2006-04-04 15:04:49 CEST: arla: worker 11 waiting
  2006-04-04 15:04:49 CEST: arla: worker 12 waiting
  2006-04-04 15:04:49 CEST: arla: worker 13 waiting
  2006-04-04 15:04:49 CEST: arla: worker 14 waiting
  2006-04-04 15:04:49 CEST: arla: worker 15 waiting
  2006-04-04 15:04:49 CEST: arla: sending version
  2006-04-04 15:04:49 CEST: arla: Send message: opcode = 0 (version), size = 20
  2006-04-04 15:04:49 CEST: arla: worker 0: processing
  2006-04-04 15:04:49 CEST: arla: Rec message: opcode = 1 (wakeup), size = 24
  libgcc_s.so.1 must be installed for pthread_cancel to work

(I configured arla with --with-pthreads). I do have a file
/lib/libgcc_s.so.1 installed, so this error message seems strange.

Accesses to /afs fail with No such device, e.g,

  nisse@maskros:~$ ls /afs
  ls: /afs: No such device

Is there any more appropriate error code that could be returned?
ENODEV made me suspect the nnpfs module, which at the moment seems to
be innocent.

What should I try next?

Regards,
/Niels