Mounting an ext3 file system destroys superblocks
Perhaps is as simple as that's the way it works and I misunderstand some basic knowlegde.
The situation is that I have an image of an ext3 file system done with dd. I know that the file system is corrupted but I want to try to recover some files. Whatever I dd it again to the original partition or assign the dd image to a loop device, that's what happens:
- dumpe2fs -h gives me a valid ext3 superblock.
- as I try to mount the device read only, it fails with a bad magic number error.
- executing dumpe2fs -h again gives bad magic number error.
- trying debugfs or fsck with backup superblocks fails the same way.
For me it seems that in spite of mounting the device as read-only, mount command do something wrong with the superblock as before the mount the superblock is correct and it's there.
¿What I'm missing?
Last edited by 0p3r4t4; 06-27-2010 at 04:39 AM.