A backup job fails with Error "E5D40024;Snap device torn down due to excessive I/O on the Volume"

Problem

Error Message

Cause

Solution

Please backup each LV (Logical Volume) in LVM separately.

For instance:
There is a volume that has multiple LVs in /dev/sda2.

# pvdisplay -C
  PV         VG           Fmt  Attr PSize  PFree
  /dev/sda2  vg_rhel64x64 lvm2 a--  59.61g    0

Note: Use "pvdisplay -C"  to show the attributes for physical volumes in LVM.

# vgdisplay -C
  VG           #PV #LV #SN Attr   VSize  VFree
  vg_rhel64x64   1   3   0 wz--n- 59.61g    0

Note: Use "vgdisplay -C"  to show the attributes for volume groups in LVM.

# lvdisplay -C
  LV      VG           Attr      LSize  Pool Origin Data%  Move Log Cpy%Sync Convert
  lv_home vg_rhel64x64 -wi-ao---  5.67g                                             
  lv_root vg_rhel64x64 -wi-ao--- 50.00g                                             
  lv_swap vg_rhel64x64 -wi-ao---  3.94g     

Note: Use "lvdisplay -C"  to show the attributes for logical volume in LVM.

# df -T
Filesystem    Type   1K-blocks    Used   Available Use% Mounted on
/dev/mapper/vg_rhel64x64-lv_root    ext4    51606140  17823140  31161560  37% /
tmpfs        tmpfs      961712        76    961636   1% /dev/shm
/dev/sdb1     ext4    62028788  17256592  41621300  30% /backup
/dev/sda1     ext4      495844     38098    432146   9% /boot
/dev/mapper/vg_rhel64x64-lv_home     ext4     5853856    144816   5411672   3% /home

Note: Use "df -T" to show the file system type of all volumes that are mounted.

Please create backup jobs like below to back up all LVs separately.

symsr -b /dev/mapper/vg_rhel64x64-lv_root -d /mnt/backup
symsr -b /dev/mapper/vg_rhel64x64-lv_home -d /mnt/backup