> I then went single user and ran fsck.ext3 on / while mounted.
> Bad move. It ran and reported many errors which I chose to repair.
> It screwed the partition up to the point where it paniced on boot.
[SNIPPED....]
You must NEVER fsck a file-system that is mounted read/write. Note,
when you `umount /`. It is still available for read/execute. You
can execute fsck at this time.
> Anyone else have luck with this combination?
> Excuse the stupid question, but with ext3, do I really require the
> fsck.ext3?
fsck.ext3 goes with ext3 file systems, just like fsck.ext2 goes with
ext2.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).
"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/