On Jan 18, 2002 10:14 +0800, Mike Lee wrote: > There are three boxes install RH7.2(kernel 2.4.7-10) say mikelee, > peanut, afssvr > > after power fail, > > only one, mikelee seem to be working right > > two fail boxes > (one, peanut already reinstall because many people depend on it, > and one, afssvr still here and fail to restart) > > mikelee log > --------------------------------------------------------------------------- > > Jan 14 09:02:52 mikelee fsck: Inode 917997, i_blocks is 64, should be 16. FIXED. > Jan 14 09:02:52 mikelee fsck: /: Inode 917999, i_blocks is 64, should be 16. FIXED. > Jan 14 09:02:52 mikelee fsck: Inode 1163457, i_blocks is 64, should be 8. FIXED. > Jan 14 09:02:52 mikelee fsck: Inode 1819135, i_blocks is 72, should be 16. FIXED. > [snip] > ---------------------------------------------------------------------------- > > > peanut log: > ---------------------------------------------------------------------------- > Jan 14 09:22:33 peanut fsck: / was not cleanly unmounted, check forced. This would indicate that the filesystem is mounted as ext2 and not ext3. What does "tune2fs -l /dev/<device>" say about this device? What does /proc/partitions show? > Jan 14 09:22:33 peanut fsck: Inode 2408738, i_blocks is 64, should be 8. FIXED. > Jan 14 09:22:33 peanut fsck: Inode 5144818, i_blocks is 64, should be 8. FIXED. > Jan 14 09:22:33 peanut fsck: /: Inode 5144819, i_blocks is 64, should be 8. FIXED. > Jan 14 09:22:33 peanut fsck: /: Inode 5144820, i_blocks is 64, should be 8. FIXED. > Jan 14 09:22:33 peanut fsck: Deleted inode 6242432 has zero dtime. FIXED. > Jan 14 09:22:33 peanut fsck: Inode 7078080, i_blocks is 96, should be 80. FIXED. > Jan 14 09:22:33 peanut fsck: /: 143780/7241728 files (1.1% non-contiguous), 986610/14458492 blocks > ---------------------------------------------------------------------------- While the number of error messages for the "mikelee" log is a bit high, both the "i_blocks is X, should be Y" and "inode N has zero dtime" errors are not unusual for an ext2 filesystem that was in use when it crashed. What they mean is (likely) that these inodes were being written to at the time the systems lost power, and there is nothing ext2 can do about this. There is nothing in the "peanut" logs which would indicate that it needed to be reinstalled. At most it would appear that there are errors with 6 files on this filesystem. It is possible that there are other errors which we can't see here that are more severe, but I can't comment on those. Do you have quota or ACL enabled on any of these systems? > afssvr can not start because some file can not be read > using RH7.2 cd and choose linux rescue option and disable several can not > start services use fsck manual it seem to be ok and pass now it can start > with many many files can not access, for examples use mc to view or edit a > file the tty is dead > nothing in lost+found I can't really say much about this, but it doesn't sound normal. I have never lost any files on my system (which has been running ext3 for more than a year now). Since it is a laptop, I often run out of batteries and do not do a complete shutdown, so I test ext3 recovery often. Cheers, Andreas -- Andreas Dilger http://sourceforge.net/projects/ext2resize/ http://www-mddsp.enel.ucalgary.ca/People/adilger/
