Copied data to LVM-Thin pool by mistake

Question

I'm here today because of a big mistake that I have made.

I created an LVM-Thin data pool (and not on a LVM-Thin LV) on my Proxmox server and (don't ask why) ran a mkfs.ext4 on the pool then mounted it on my local node. After that I copied a bunch of data on it and stopped my system:

mkfs.ext4 /dev/mapper/pve-data
mount /dev/mapper/pve-data /mnt/data/
cp -r Temp/ /mnt/data/

The next time I created a VM on this pool from the Proxmox GUI, and you guessed it, found out what I had done too late.

I tried to mount the pool again (even if that shouldn't be possible) without any success as you can guess:

lvm thin mount: *: wrong fs type, bad option, bad superblock on /dev/mapper/*, missing codepage or helper program, or other error.

Tried mount -t ext4 /dev/mapper/pve-data /mnt/data too.

I searched if I could restore the FS on it with a fsck or something but didn't do it by fear of making my data inaccesible forever.

Finally I tried to use PhotoRec on my disks, but because of the time it takes to run I stopped it.

I wanted to know if there was something else to do (with fsck for exemple) before letting PhotoRec run for days on my disks?

Could you help me?

How it is ever possible to access the volume for creating file system and mounting after it was converted to the thin pool data LV? — Nikita Kipriyanov, Feb 27 '23 at 08:47
Don’t know myself why it was allowed by the system. It was a case of figure not taken into account. — Hidd, Feb 27 '23 at 09:50

score 1 · Accepted Answer · answered Feb 27 '23 at 08:24

1

You trashed your data-containing volume, so you are not going to see its data again. You must restore from backup.

answered Feb 27 '23 at 08:24

shodanshok

47,711
7
111
180

I think so too. I will have to try working with PhotoRec. If I find something I will write it here. If not I will mark your answer as the correct one. Thanks. – Hidd Feb 27 '23 at 09:51

Copied data to LVM-Thin pool by mistake

1 Answers1