Hi. Few minutes ago, being too tired, I unfortunately did a mkfs.ext3 on an already existing ext3 fs (instead of fsck.ext3). It unfortunately didn't warn me that there's already an fs on it but started right away with it's evil work[0] until I ^C-ed it[0] in panic. I know this list is about devel, but unfortunately I don't know a better place to ask experts (sorry). When I scan the fs with testdisk it seems to find some superblocks, having the old fs label: superblock 32768, blocksize=4096 [data1] superblock 98304, blocksize=4096 [data1] superblock 163840, blocksize=4096 [data1] superblock 229376, blocksize=4096 [data1] superblock 294912, blocksize=4096 [data1] superblock 819200, blocksize=4096 [data1] superblock 884736, blocksize=4096 [data1] superblock 1605632, blocksize=4096 [data1] superblock 2654208, blocksize=4096 [data1] superblock 4096000, blocksize=4096 [data1] Could it be that these are still valid ones? When I try to mount e.g.: # mount -t ext3 -o sb=$((32768*4)) /dev/sdc1 /mnt/ mount: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so ...it doesn't work however. Any ideas? Thanks, Chris. btw: Please CC me as I'm off list. [0]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 45793280 inodes, 183143000 blocks 9157150 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=4294967296 5590 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 Writing inode tables: ^C00/5590 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html