cancel
Showing results for 
Search instead for 
Did you mean: 

backup exec error

seighalani
Level 3

hi everyone

I installed backup exec 16 on windows2012 R2  and take backup from a physical client (Red Hat 6.4) . on red hat 6.4 recieve these error messages:

Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: EXT4-fs error (device snap253_65): __ext4_get_inode_loc: unable to read inode block - inode=2, block=353
Sep 23 09:24:37 pm-db-2 kernel: Failed to get the sSD info
Sep 23 09:24:37 pm-db-2 kernel: Failed to get the sSD info
Sep 23 09:24:37 pm-db-2 kernel: EXT4-fs error (device snap253_0): __ext4_get_inode_loc: unable to read inode block - inode=2, block=1057
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: EXT4-fs error (device snap253_66): __ext4_get_inode_loc: unable to read inode block - inode=2, block=353
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: EXT4-fs error (device snap253_66): __ext4_get_inode_loc: unable to read inode block - inode=2, block=353
Sep 23 09:24:37 pm-db-2 kernel: Failed to get the sSD info
Sep 23 09:24:37 pm-db-2 kernel: Failed to get the sSD info
Sep 23 09:24:37 pm-db-2 kernel: EXT4-fs error (device snap253_0): __ext4_get_inode_loc: unable to read inode block - inode=2, block=1057
Sep 23 09:24:37 pm-db-2 kernel: Failed to get the sSD info
Sep 23 09:24:37 pm-db-2 kernel: Failed to get the sSD info
Sep 23 09:24:37 pm-db-2 kernel: Failed to get the sSD info
Sep 23 09:24:37 pm-db-2 kernel: Failed to get the sSD info
Sep 23 09:24:37 pm-db-2 kernel: EXT4-fs error (device snap253_0): __ext4_get_inode_loc: unable to read inode block - inode=2, block=1057
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: Initializing Symbdsnap resources..
Sep 23 09:24:37 pm-db-2 kernel: EXT4-fs error (device snap253_67): __ext4_get_inode_loc: unable to read inode block - inode=2, block=1057

when stop veritas service (VRTSralus.init)  on rhel6.4 and restart it . afterthat these error messages will remove but when start service and take backup it will show again. what should i do for that ?thanks in advance

 

5 REPLIES 5

seighalani
Level 3

anyone help?

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

This seems to be a Linux Filesystem error.

Please show this to the Linux admin:

EXT4-fs error (device snap253_65): __ext4_get_inode_loc: unable to read inode block - inode=2, block=353

this error  apeared when backupexec verifying  backup. in verifying step  these errors apeared.

snap devices (snapshot ) related to  backupexec not filesystem. these errors only apear  when you run backupexec agent and take backup from backupexec server.

anyone help?