Hey, In some stupid late night adventures, I accidentally ran mke2fs on my normal /home volume (1.3TB, about 600GB used....) rather than a new volume I had intended... I quickly realized my mistake and did ^C though I'm not sure what my options are now for possible recovery.... # mkfs.ext4 /dev/freedom/home mke2fs 1.41.12 (17-May-2010) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 85196800 inodes, 340787200 blocks 17039360 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=0 10400 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000, 214990848 Writing inode tables: ^C 41/10400 # "dumpe2fs -o superblock=20480000" seems to give the old superblock metadata still... filesystem create time, last write, etc, though running e2fsck results in this: # e2fsck -n -b 20480000 /dev/freedom/home e2fsck 1.41.12 (17-May-2010) Superblock has an invalid journal (inode 8). Clear? no e2fsck: Illegal inode number while checking ext3 journal for /dev/freedom/home I'm in a panic and I don't know what to do.. if anyone can help recover data from this accident it would be much appreciated -- 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
