All that RPM bashing for nothing :)
Have you tried running e2fsck by hand on the partiton(s)? I once had a
machine that did that to me, but once I fscked it by hand, it was fixed.
See /usr/src/linux/Documentation/oops-tracing.txt to see haow to get info
from that oops.
hth
charles
On Thu, 2 Mar 2000, Ward William E PHDN wrote:
> Ok, I've been really working the RPM problem, and have solved everything up
> to one
> point... the new error message that I started getting, about the disk being
> full.
> I've done some experiments, and somehow, not only did the rpm database get
> corrupted,
> but the filesystem has become corrupted. I can create files, write to them,
> etc.,
> but I cannot create new directories. I've never seen anything like that.
> I've
> tried rebooting, thinking it was some kind of transient error, and fsck has
> detected
> errors on the disk... repeatedly. Every time I've rebooted, even if I
> reboot, login
> just as root and as the first thing I do I tell it to reboot again, I get
> fsck
> reporting errors on the disk. Fsck should have repaired them; it didn't.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
