XFS Volume via LVM - Something happened.

[TheBigAmbulance]

For whatever reason, my LVM has stopped functioning, but appears to still be there. A careless /dev/mapper/X file was removed, and stopped the LVM dead in it's tracks.

root@farsrv333:/etc/lvm/backup# mount -a
mount: /dev/mapper/vgstorage-lvstorage: can't read superblock
root@farsrv333:/etc/lvm/backup# xfs_repair /dev/v
vcs          vcs3         vcs6         vcsa1        vcsa4        vcsa7        vhost-net    
vcs1         vcs4         vcs7         vcsa2        vcsa5        vga_arbiter  
vcs2         vcs5         vcsa         vcsa3        vcsa6        vgstorage/   
root@farsrv333:/etc/lvm/backup# xfs_repair /dev/vgstorage/lvstorage 
Phase 1 - find and verify superblock...
superblock read failed, offset 0, size 524288, ag 0, rval 0

fatal error -- Invalid argument
root@farsrv333:/etc/lvm/backup# vgscan
  Reading all physical volumes.  This may take a while...
  Found volume group "vgstorage" using metadata type lvm2
root@farsrv333:/etc/lvm/backup# pvscan
  PV /dev/sdb1    VG vgstorage   lvm2 [2.73 TiB / 0    free]
  PV /dev/sdc1    VG vgstorage   lvm2 [2.73 TiB / 0    free]
  PV /dev/sda10   VG vgstorage   lvm2 [659.27 GiB / 0    free]
  Total: 3 [6.10 TiB] / in use: 3 [6.10 TiB] / in no VG: 0 [0   ]
root@farsrv333:/etc/lvm/backup#

To my eye, it looks like the data is still there. I do have backups and archives:

root@farsrv333:/# ls -la /etc/lvm/backup/
total 12
drwx------ 2 root root 4096 Mar 28 12:04 .
drwxr-xr-x 5 root root 4096 Mar 12 08:12 ..
-rw------- 1 root root 2012 Mar 28 12:04 vgstorage
root@farsrv333:/# ls -la /etc/lvm/archive/
total 72
drwx------ 2 root root 4096 Mar 28 12:04 .
drwxr-xr-x 5 root root 4096 Mar 12 08:12 ..
-rw------- 1 root root  839 Mar 12 08:12 vgstorage_00000.vg
-rw------- 1 root root  848 Mar 12 08:12 vgstorage_00001.vg
-rw------- 1 root root 1177 Mar 12 08:17 vgstorage_00002.vg
-rw------- 1 root root  829 Mar 12 08:17 vgstorage_00003.vg
-rw------- 1 root root  839 Mar 12 08:32 vgstorage_00004.vg
-rw------- 1 root root  848 Mar 12 08:32 vgstorage_00005.vg
-rw------- 1 root root 1177 Mar 12 08:35 vgstorage_00006.vg
-rw------- 1 root root  854 Mar 12 08:37 vgstorage_00007.vg
-rw------- 1 root root 1181 Mar 13 12:42 vgstorage_00008.vg
-rw------- 1 root root 1426 Mar 13 12:56 vgstorage_00009.vg
-rw------- 1 root root 1181 Mar 13 12:57 vgstorage_00010.vg
-rw------- 1 root root 1444 Mar 13 12:58 vgstorage_00011.vg
-rw------- 1 root root 1607 Mar 14 09:17 vgstorage_00012.vg
-rw------- 1 root root 1871 Mar 14 09:19 vgstorage_00013.vg
-rw------- 1 root root 2013 Mar 28 12:04 vgstorage_00014.vg
-rw------- 1 root root 2013 Mar 28 12:04 vgstorage_00015.vg
root@farsrv333:/#

Can I rebuild the missing block device using this data? Could I simply remove the LVM and readd the disks to a new LVM?

[TheBigAmbulance]

sigh... here is what happened...

dmsetup remove /dev/mapper/36001a620000242313430364230313532

Any easy way to recover from this....?