On Tue, 2006-12-12 at 16:16 +0100, Alexander Verkooijen wrote:
> According to the manual this is the meaning
> of return code 4:
>
> ------------------------
> The operation completed successfully, but some files were
> not processed. There were no other errors or warnings.
> This return code is very common. Files are not processed
> for various reasons. The most common reasons are:
>
> The file is in an exclude list.
>
> The file was in use by another application and could
> not be accessed by the client.
>
> The file changed during the operation to an extent
> prohibited by the copy serialization attribute.
> See Copy serialization.
> ------------------------
>
> Maybe you should check dsmsched.log and/or dsmerror.log
> on your client to see which files aren't backed up and
> why.
>
Sigh, I'm an idiot. Or overworked, or something :)
The dsmerror.log has
12/12/06 02:11:44 ANS1076E *** Directory path not found ***
12/12/06 04:57:15 ANS1512E Scheduled event 'UNIX_NIGHTLY' failed. Return
code 4
and sure enough, after we were moving some filesystems around I forgot
to change the domains in dsm.opt.
Thanks for the wakeup call :)
Brian
> Regards,
>
> Alexander
>
> ------------------------------------------------------------
> Alexander Verkooijen
> Senior Systems Programmer
> High Performance Computing
> SARA Computing & Networking Services
>
>
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]
> > On Behalf Of Brian Wheeler
> > Sent: Tuesday, December 12, 2006 3:40 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: ANR2579E backup "fails"
> >
> > Every night we have one machine which fails with return code 4, but I
> > cannot figure out why. Its the only machine that does this,
> > and we have
> > several with the same configuration. The versions we're using are:
> >
> > Server version 5.1.6
> > Client version 4.2.1
> >
> > Here's the activity log entries for last night for this node
> > that fails.
> > There's nothing obvious as to why it fails. Any other places I should
> > look to try to diagnose this?
> >
> > Thanks!
> > Brian Wheeler
> >
> >
> >
> > 12/12/06 02:11:43 ANR0406I Session 220 started for node
> > ERATO (AIX) (Tcp/Ip
> > 156.56.241.23(59710)).
> > 12/12/06 02:11:54 ANR0406I Session 221 started for node
> > ERATO (AIX) (Tcp/Ip
> > 156.56.241.23(59712)).
> > 12/12/06 04:57:14 ANR0403I Session 221 ended for node ERATO (AIX).
> > 12/12/06 04:57:15 ANE4952I (Session: 220, Node: ERATO)
> > Total number of
> > objects inspected: 1,219,474
> > 12/12/06 04:57:15 ANE4954I (Session: 220, Node: ERATO)
> > Total number of
> > objects backed up: 905
> > 12/12/06 04:57:15 ANE4958I (Session: 220, Node: ERATO)
> > Total number of
> > objects updated: 0
> > 12/12/06 04:57:15 ANE4960I (Session: 220, Node: ERATO)
> > Total number of
> > objects rebound: 0
> > 12/12/06 04:57:15 ANE4957I (Session: 220, Node: ERATO)
> > Total number of
> > objects deleted: 0
> > 12/12/06 04:57:15 ANE4970I (Session: 220, Node: ERATO)
> > Total number of
> > objects expired: 59
> > 12/12/06 04:57:15 ANE4959I (Session: 220, Node: ERATO)
> > Total number of
> > objects failed: 0
> > 12/12/06 04:57:15 ANE4961I (Session: 220, Node: ERATO)
> > Total number of
> > bytes transferred: 11.66 GB
> > 12/12/06 04:57:15 ANE4963I (Session: 220, Node: ERATO)
> > Data transfer time:
> > 5,484.59 sec
> > 12/12/06 04:57:15 ANE4966I (Session: 220, Node: ERATO)
> > Network data
> > transfer rate: 2,230.35 KB/sec
> > 12/12/06 04:57:15 ANE4967I (Session: 220, Node: ERATO)
> > Aggregate data
> > transfer rate: 1,231.63 KB/sec
> > 12/12/06 04:57:15 ANE4968I (Session: 220, Node: ERATO)
> > Objects compressed
> > by: 0%
> > 12/12/06 04:57:15 ANE4964I (Session: 220, Node: ERATO)
> > Elapsed processing
> > time: 02:45:32
> > 12/12/06 04:57:15 ANR2579E Schedule UNIX_NIGHTLY in
> > domain SERVERS for node
> > ERATO failed (return code 4).
> > 12/12/06 04:57:16 ANR0403I Session 220 ended for node ERATO (AIX).
> > 12/12/06 04:57:16 ANR0406I Session 303 started for node
> > ERATO (AIX) (Tcp/Ip
> > 156.56.241.23(59778)).
> > 12/12/06 04:57:16 ANR0403I Session 303 ended for node ERATO (AIX).
> >
|