Nope, Charles, there was something wrong with RPM.... I've just
FIXED that part, thanks to a few pointers as to what to look for
in rpm.conf, etc.  At least, I >THINK< I did.  But whatever 
screwed up rpm seems to have also done a number elsewhere on
the drive... or perhaps, the drive did a thing on rpm.conf,
though I find that hard to believe.

BTW, if anyone is wondering.... this machine is behind three
seperate firewalls, so I'm pretty sure that it's not been
hacked.  I don't control the firewalls, but the only thing
they let through is incoming email and http answers, and ditto
on the only thing going out.

Paranoia for once pays off, I guess, in that I can eliminate those
possibilities easily. :\

Bill Ward

-----Original Message-----
From: Charles Galpin [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 02, 2000 10:28 AM
To: Redhat-List (E-mail)
Cc: recipient.list.not.shown; @nswcphdn.navy.mil
Subject: Re: Non-fsck disk repair tools?


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.


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to