From: mike@ws.rz.tu-bs.de (Mike Dowling) Subject: e2fs Problems/Queries Date: Wed, 14 Apr 1993 19:42:06 GMT
I have just finished porting my entire linux configuration from old MFM hard
disks to a new AT bus disk, and am trying ext2 for the first time.
Unfortunately, when turning off the kettle, by force of habit, I turned off the
power at the mains, and caused my linux to crash. On rebooting, I had some
strange effects.
Firstly, e2fsck noted that my root partition was not ok. It corrected the
problem. Calling e2fsck twice for the same partition, however, resulted it
e2fsck again thinking that the fs was not ok, and again it wanted to correct
it. I also used e2fsck on the /usr fs, but with the same effect. Silly of me,
thought I; I should boot from a diskette and then run e2fsck on an unmounted
partition.
I booted from disk, and tried e2fsck on root. Again it corrected errors. The
second time, though, after the checking, it reported no further errors. I then
ran e2fsck on /usr. After a while, I got "out of memory" errors (I have 8 MB),
and my system hanged.
Pushed the reset button, rebooted from dikette. I altered /etc/fstab and
/etc/rc to avoid mounting /usr automatically when booting, and then booted from
the hard disk. I ran e2fsck on both partitions. After initial errors on /usr,
e2fsck apparently no longer finds errors. In nevertheless never thinks that
the partitions are clean, and continues to insist of checking everything in
full before coming to the conclusion that things are ok.
Question: How do I get e2fsck to immediately recognise that both partitions are
clean?
Question: Worse, is the fact the e2fsck (0.2d) does not regognise the partions
are being clean an indication that permanent damage to the fs has been done?
Mike Dowling
i1041301@ws.rz.tu-bs.de