Comment 3 for bug 1375640

Thank you for the information.
I was thinking, that I have destroyed the extents and other features of the ext4 file system by using a tool that is not aware of the special ext4 features, leading to filesystem coruption.
What happens, if I hit CTRL-C during fsck? Can that leave the filesystem in a even more inconsistent state?

I used a SSD, so it is likely that resetting the system could have damaged the file system.
Probably it is a good idea to keep the /home directory on a separate partition.
This is how I used to do; when there was file system corruption in the past (mostly dying disks), the root filesystem got broken, but the home partition only had none or minor issues, so recovery was always easy.
But it is not the default when installing ubuntu and for this installation I didn't care for it.

Also the nvidia driver could have caused the damage by overwriting memory which finally led to the crash.
But if that was nvidia driver's memory corruption, it is likely that it could also also hit a separate home partition or any other mounted drive.

Is there a way to recover the file system manually? There is still hope that the areas with data are mostly still present. I still keep a copy of the disk image and I am still trying some recovery tools on a copy of that image.

fsck.ext4 resulted in that some data still exists, some files have gone to lost+found , but many files seem to be lost (the partition now appears to be mostly unused).
It seems that much space has been unallocated and as a result some files could have been partially overwritten during system boot, when the system writes to the disk.

As far as I know, fsck.ext4 does not scan the whole disk for files to be linked to lost+found, but only these areas that have been marked as used to improve speed.
Is it possible to force searching the whole disk image for existing fragments of the file system that are not allocated as used and do not have any linkage to the existing filesytem any more?
I know that this could deliver much garbage (very old files) that have been deleted or overwritten far before and are not of use, but probably it could be useful to recover some useful data where the linkage to the file system has been lost and that have been unallocated by filesystem coruption.

Could you provide me a link to current documentation of ext4 and fsck? Where can I get the sources?

Can you recommend some good open source recovery tools?