On Sun, Feb 21, 2010 at 03:00:15PM +0100, Albert Sellarès wrote: > > e2fsck quits after the bad magic number message. I didn't pasted the > entire e2fsck output (sorry!). The full output was that: > > root@pacs:~# e2fsck -C 0 -y -t /dev/storage/cabina_snapshot2 > e2fsck 1.41.9 (22-Aug-2009) > /dev/storage/cabina_snapshot2 contains a file system with errors, check > forced. > Pass 1: Checking inodes, blocks, and sizes > /dev/storage/cabina_snapshot2: |================== / 60.0% > > [...] > > Until 60% of the progress bar, there was no error messages. After reach > the 60%, e2fsck started fixing a lot of things. In the output I > recognized the inode that it was analyzing. Once e2fsck analyzed the > last inode of the filesystem, it printed this message and exited: So *do* you have the full e2fsck output? I'd like to look at it to see what it did. It's _possible_ that a really badly corrupted file system block might have caused it to get confused enough such that it managed to overwrite the superblock while trying to fix the filesystem. But unless I see the whole e2fsck output, it's hard to say for sure what happened. - Ted _______________________________________________ Ext3-users mailing list Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
