18.2 FLR FindMountPathInFstab fails when FSTAB has -- in LV

           

   Article Number:     534850                                   Article Version: 2     Article Type:    Break Fix 
   

 


Product:

 

Integrated Data Protection Appliance

 

Issue:

 

 

   

      FLR FindMountPathInFstab fails when Fstab entry has –- in LV Name. Error in MountPoint log :- [MM - DEBUG] 2019/05/07 14:47:25 TID=140239272170242 MID=2022809: DEVICE_ID_TYPE_LVM FOUND: /dev/vg0/lv_var-log[MM - DEBUG] 2019/05/07 14:47:25 TID=140239272170242 MID=2022810: sBuf = /dev/mapper/vg0-lv_var--log /var/log                ext4    defaults        1 2[MM - DEBUG] 2019/05/07 14:47:25 TID=140239272170242 MID=2022854: DEVICE_ID_TYPE_LVM FOUND: /dev/vg0/lv_var-log[MM - DEBUG] 2019/05/07 14:47:25 TID=140239272170242 MID=2022840: sBuf = /dev/mapper/vg0-lv_mysqlback  /var/lib/mysql/backups     ext4    defaults        1 2[MM - DEBUG] 2019/05/07 14:47:25 TID=140239272170242 MID=2022855: sBuf =[MM - ERROR] 2019/05/07 14:47:25 TID=140239272170242 MID=2022856: FindMountPathInFstabByDevice Failed[MM - FUNC] 2019/05/07 14:47:25 TID=140239272170242 MID=2022857: VmdkDiskLinux::FindMountPathInFstabByDevice LEAVE[MM - ERROR] 2019/05/07 14:47:25 TID=21250 MID=2022858: FindMountPathInFstabByDevice Failed[MM - FUNC] 2019/05/07 14:47:25 TID=21250 MID=2022859: VmdkDiskLinux::MakePartitionToSymlinkAssoc LEAVE[MM - ERROR] 2019/05/07 14:47:25 TID=21250 MID=2022860: RestoreMountPoints Failed[MM - FUNC] 2019/05/07 14:47:25 TID=21250 MID=2022861: VmdkDiskLinux::RestoreMountPoints LEAVE    
                                                             

 

 

Cause:

 

 

   

      When you create a Logical Volume for eg  using lvcreate which contains hyphen in LV name, blkid and /dev/mapper appends extra “-” and when fstab entry is created with that FLR code fails to verify fstab entry.     
                                                             

 

 

Resolution:

 

 

There was a double hyphen issue in avamar FLR tab restore so installed the hotfix HF # 310157 and the issue was resolved