Forum Discussion

Hamza_H's avatar
Hamza_H
Moderator
4 years ago
Solved

Errors in storaged.log

Hello,

I have a question regarding an error that was found in storaged.log :

failed to find container node ID for container 0

Do you have any idea what could cause this error? corrupted images? 

NB version 8.1.

The latest version of the bundle 3935219 is installed.

 

Thanks,

 

 

8
Linux
  • davidmoline's avatar
    davidmoline
    4 years ago

    Hi Hamza_H 

    I've seen similar errors in a test environment I use - and in my case I found a number of orphaned images (probably due to syustem crashes and the like). Once I tidied up (removed) these images, the errors have not returned. 

    There are two tools that I know of, one specifically to look for orphaned images (PoGather which is run on your master and media servers and then analysed by Veritas using Imgchk), the other is msdpcheck which does what it name implies. Both are only available from support. 

    So yes - I ask Veritas to investigate - better to be safe than sorry. 

    Interesting aside - I had one customer that was using a cloud catalyst and had almost filled their S3 store (so almost 1PB of cloud based images). This didn't make sense looking at their catalog and dedupe rates, and after running the PoGather, they were able to recover 100's of TB of cloud storage due to orphaned images. 

    Cheers
    David

  • pats_729's avatar
    pats_729
    Level 6
    4 years ago

    Hamza_H 

    Usually in logs strings appears with "[ERR]" or "[INFO]" or "[WARN]". It depicts the severity of the message.

    How is this line appearing for you in logs ?

    Besides,  are you observing any failures or malfunctions ?

    • Hamza_H's avatar
      Hamza_H
      Moderator
      4 years ago

      Hello pats_729, 

      It appears as ERR :

      August 05 12:30:56 ERR [140127557904128]: -1: failed to find container node ID for container 0

      We are not observing any failures or malfunctions (yet)..

      Thanks;

      • davidmoline's avatar
        davidmoline
        Level 6
        4 years ago

        Hi Hamza_H 

        The fact that there are errors being reported is not good, but doesn't necessarily indicate corruption.

        Check to see if there is anything in the following file <PATH_TO_MSDP>/databases/datacheck/AffectedBackup.lst

        If there are entries it indicates a possible issue such as orphaned images etc. The recommendation then is to log a support case to get the required tools to analyse and fix any issue under guidance. 

        Cheers
        David