recovering corrupt file system

Keld Simonsen keld at
Fri Nov 20 18:48:40 UTC 2015

On Fri, Nov 20, 2015 at 03:06:16AM +0000, Boylan, Ross wrote:
> I tried the "just run e2fsck", but it reduced the filesystem to almost nothing.  Before there were nearly 700G of files; after there were 70G.*  Also, the overall filesystem size shrunk to under 300G.  I ran resize2fs to  get the  space back, but of course that didn't get the files back.
> This seems like an awful lot of damage from losing a total of 8,192 bytes out of ~700G.  Maybe the first block of zeros caused the recovery to decide it had reached the end?  The logical volume got about 64GB from the first, presumably OK, virtual disk.  The holes in the file occur around 174GB into the 2nd virtual hard disk.
> I've still got copies from before e2fsck, and I'm still interested in recovering them (lots of recorded shows on them).
> Sorry about the top-posting; my mail client doesn't provide good way to do otherwise.
> Ross
> *I had expected only to lose the newer files, but a lot of the program files seem to be gone too. startx doesn't exist, for example.

I once made som patches to recover files from a corrupted ext3 file system.
But I did not get it into the main branch and it is not maintained.
But you could try it out. I am not sure if it is any good for an ext4 FS.

Best regards

More information about the Ext3-users mailing list