Opened 3 years ago

Closed 3 years ago

#1839 closed help (fixed)

Odd compilation error

Reported by: simon.tett Owned by: annette
Priority: normal Component: Disk Space
Keywords: Cc:
Platform: ARCHER UM Version: 7.8

Description

Hi,

I'm getting the following error when I try and compile my job xlwt#s. I've done a full extract build and deleted the um directory so all is as clean as I can manage.

Partial output from the comp.leave file:
# Start: 2016-03-21 09:49:54⇒ ftn -o max_calls.o -I/home/n02/n02/stett2/um/xlwts/ummodel/inc -I/home/n02/n02/stett2/um/xlwts/umbase/inc -e m -h noomp -s real64 -s integer64 -hflex_mp=intolerant -I /work/n02/n02/hum/gcom/cce/gcom3.8/archer_cce_mpp/inc -c /home/n02/n02/stett2/um/xlwts/ummodel/ppsrc/UM/atmosphere/radiation_control/max_calls3z.f90
ftn-3121 crayftn: LIMIT MAX_CALLS_, File = ../../../../../../../../home2/n02/n02/stett2/um/xlwts/ummodel/ppsrc/UM/atmosphere/radiation_control/max_calls3z.f90, Line = 1

There is a problem with a temp file being used in compilation.

fcm_internal compile failed (256)
# Time taken: 2 s⇒ ftn -o max_calls.o -I/home/n02/n02/stett2/um/xlwts/ummodel/inc -I/home/n02/n02/stett2/um/xlwts/umbase/inc -e m -h noomp -s real64 -s integer64 -hflex_mp=intolerant -I /work/n02/n02/hum/gcom/cce/gcom3.8/archer_cce_mpp/inc -c /home/n02/n02/stett2/um/xlwts/ummodel/ppsrc/UM/atmosphere/radiation_control/max_calls3z.f90
gmake: * [max_calls.o] Error 1

I wonder if this might be called by having a flush(6) in a piece of code. Added in an attempt to get some more output out of the model to understand why it is crashing..

So when I remove the flush(6) I still get compilation errors of the form:
/work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s: Assembler messages:
/work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s: Warning: end of file in string; '"' inserted
/work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:45: Error: junk at end of line, first unrecognized character is `"'
/work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:60: Error: invalid character (0x9) in mnemonic
/work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:61: Error: invalid character (0x9) in mnemonic
/work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:64: Error: invalid character (0x9) in mnemonic
/work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:65: Error: invalid character (0x9) in mnemonic
/work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:66: Error: invalid character (0x9) in mnemonic
/work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:67: Error: invalid character (0x9) in mnemonic
/work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:69: Error: invalid character (0x9) in mnemonic
/work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:70: Error: invalid character (0x9) in mnemonic
/work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:71: Error: invalid character (0x9) in mnemonic
/work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:72: Error: invalid character (0x9) in mnemonic
/work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:74: Error: invalid character (0x9) in mnemonic
/work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:75: Error: invalid character (0x9) in mnemonic
/work/n02/n02/stett2/tmp/tmp.esPP002.20547/pe_43862/dust_parameters_mod_1.s:80: Error: invalid character (0x9) in mnemonic

and then..
# Start: 2016-03-21 10:09:07⇒ ftn -o lwrdiag_mod.o -I/home/n02/n02/stett2/um/xlwts/ummodel/inc -I/home/n02/n02/stett2/um/xlwts/umbase/inc -e m -h noomp -s real64 -s integer64 -hflex_mp=intolerant -I /work/n02/n02/hum/gcom/cce/gcom3.8/archer_cce_mpp/inc -c /home/n02/n02/stett2/um/xlwts/ummodel/ppsrc/UM/atmosphere/radiation_control/lwrdiag_mod.f90
fcm_internal compile failed (256)
# Time taken: 5 s⇒ ftn -o dust_parameters_mod.o -I/home/n02/n02/stett2/um/xlwts/ummodel/inc -I/home/n02/n02/stett2/um/xlwts/umbase/inc -e m -h noomp -s real64 -s integer64 -hflex_mp=intolerant -I /work/n02/n02/hum/gcom/cce/gcom3.8/archer_cce_mpp/inc -c /home/n02/n02/stett2/um/xlwts/ummodel/ppsrc/UM/atmosphere/aerosols/dust_parameters_mod.f90
gmake: * [dust_parameters_mod.o] Error 1

If I compile dust_parameters_mod.f90 on the front end it works fine..

stett2@eslogin003:~/um> ftn -o dust_parameters_mod.o -I/home/n02/n02/stett2/um/xlwts/ummodel/inc -I/home/n02/n02/stett2/um/xlwts/umbase/inc -e m -h noomp -s real64 -s integer64 -hflex_mp=intolerant -I /work/n02/n02/hum/gcom/cce/gcom3.8/archer_cce_mpp/inc -c /home/n02/n02/stett2/um/xlwts/ummodel/ppsrc/UM/atmosphere/aerosols/dust_parameters_mod.f90
stett2@eslogin003:~/um>

So help….

Simon

Change History (3)

comment:1 Changed 3 years ago by simon.tett

I wonder if this (and other errors) are due to running out of quota. I keep throwing jobs at archer to try and compile some more… I note hte following message in my latest job:
libcif: error positioning file /fs2/n02/n02/stett2/tmp/tmp.esPP002.60014/pe_61815/atm_fields_bounds_mod.T - Disk quota exceeded

But my quota is fine:
stett2@eslogin003:~/um> quota -s
Disk quotas for user stett2 (uid 14668):

Filesystem blocks quota limit grace files quota limit grace

netapp1:/vol/vol2

184M 10240M 10240M 2872 4295m 4295m

and checking out /fs2/n02/n02/stett2 I have a bunch of old directories so I removed them. Resubmittted compile job and it seems to be running now…

comment:2 Changed 3 years ago by annette

  • Component changed from UM Model to Disk Space
  • Owner changed from um_support to annette
  • Status changed from new to assigned

Hi Simon,

It looks like you have figured this one out yourself so I will close the ticket. The UM code is quite large and can easily fill up the home space but you should be able to safely delete old build directories as the execs are copied over to work.

Annette

comment:3 Changed 3 years ago by annette

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.