On Sep 20, 2007 17:36 -0400, Thomas Watt wrote: > Using dumpe2fs I have been able to determine that all of my alternate > ext3 superblocks are corrupted (not clean), and only the primary > superblock is valid, i.e. mount works and the ordered journal is applied. > When the primary superblock gets flakey, i.e. the ext_attr Filesystem > feature goes missing - not sure why this occurs. At this point, the > mount does not apply the journal using the primary superblock and mount > completes without it. Usually, I will resort to booting up the FC3 > OS hard drive on which the ext3 filesystem resides to fix at least the > primary superblock via fsck. Normally the superblock backups are touched only when e2fsck runs. This ensures that the backups are not touched by the kernel and not also "updated" with corruption in case of a software/hardware problem. The only code I know that updates the backup superblocks is the online resizing code, because if it doesn't the backup copies will no longer be useful (i.e. any data written beyond the old end-of-filesystem would be lost). > Will the command: e2fsck -fp /dev/sdb2 repair the alternate superblocks, > and if so, should it only be run from the Live CD environment? Or, > do I need to get into runlevel 1 as single user to issue the command > after unmounting the hard drive in order to run it? The e2fsck should handle it. Can you post the differences between the bad and good superblocks before you do so? Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. _______________________________________________ Ext3-users mailing list Ext3-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ext3-users
