Displaying 1 result from an estimated 1 matches for "e2sck".
Did you mean:
e2fsck
2010 Jan 04
0
ext3 resize failed, data loss
...free space than it should have, and it couldn't complete
an fsck (and was obviously not safe to use mounted rw lest it try to
write to space it didn't actually own). Google turned up some accounts
of people with the identical issue, and suggestions to fix it by
writing a new superblock with e2sck -S, then fscking - I did this, and
it totally trashed my filesystem. The fs is now the right size and
mounts fine, but everything just got dumped into lost+found.
Is there any way I can fix this and get my data back? At least get it
back to its previous state so I can mount it ro and copy my data...