How to Solve Linux resize2fs error: Bad magic number in super-block

[root@backup binlog]# vgdisplay
— Volume group —
VG Name centos
System ID
Format lvm2
Metadata Areas 2
Metadata Sequence No 8
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 3
Open LV 3
Max PV 0
Cur PV 2
Act PV 2
VG Size 2.73 TiB
PE Size 4.00 MiB
Total PE 715273
Alloc PE/Size 712822/2.72 TiB
Free PE/Size 2451/9.57 GiB
VG UUID 6rIzMZ-cqff-oWy6-0EvS-YENe-37U9-65SunU

[root@backup binlog]# lvextend -L +4G /dev/mapper/centos-home
Size of logical volume centos/home changed from 2.66 TiB (697542 extents) to 2.66 TiB (698566 extents).
Logical volume home successfully resized.

Error executing resize2fs:
[root@backup binlog]# resize2fs /dev/mapper/centos-home
resize2fs 1.42.9 (28-Dec-2013)
resize2fs: Bad magic number in super-block

When trying to open /dev/mapper/centos-home
no valid filesystem superblock is found.

Make sure the file system is xfs:
[root@backup binlog]# cat /etc/fstab | grep centos-home
/dev/mapper/centos-home /home xfs defaults 0 0

xfs uses the following command to expand disk space:
[root@backup binlog]# xfs_growfs /dev/mapper/centos-home
meta-data=/dev/mapper/centos-home isize=256 agcount=6, agsize=118277632 blks
= sectsz=4096 attr=2, projid32bit=1
= crc=0 finobt=0
data = bsize=4096 blocks=709040128, imaxpct=5
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=0
log =internal bsize=4096 blocks=231011, version=2
= sectsz=4096 sunit=1 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
data blocks changed from 709040128 to 715331584