On Fri, Feb 10, 2012 at 06:36:52PM +0000, Rudolf Zran wrote: > >> * "fsck.ext4 -b $SBOK -B 4096 -v -y /dev/loop0" recoveres after a long time. > >> Filesystem is mountable. Root is empty besides lost+found folder, which > >> contains about 300GB mostly useless data: Millions of files with wrong > >> permissions, useless names and some random content. > > > I'd do this by making a copy of the file system first, of course…. I would have expected at least some subdirectories from your directory hierarcy that contained useful content. Just to set expectations, things that you might do that tried to look for directory blocks, etc., *might* give you more useful filenames as opposed to random inode numbers in lost+found, but it's unlikely to recover any more *files*. It sounds most of your files were located in part of the inode table that got smashed, and so short of looking at each data block to find useful bits, I doubt spending a lot of time on trying to use or create more recovery tools based on file system metadata is likely to result in more data getting recovered. - Ted P.S. e2fsck -n by definition opens the block device read-only, so it's not at all surprising you couldn't mount it after e2fsck -n; it wouldn't have changed anything. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
