Unix Permission Problem After a CPU Crash

[Fairlight]

Confusious (Del) say:
>
> I am assuming that the operating system was doing something to that
> file when the system crashed, and that it was locked somehow during the
> operation and never got unlocked.  I don't know who user "103" is, but it
> must be operating system related, and it is a user that even locks out
> root.

I don't know why you're making that assumption, but it's probably not
valid.  Based on the behaviour in general, I'd say the inode may be
corrupt.  Have you run an fsck on the partition in question?

> Can anybody shed light on what is going on here?  I have never seen
> anything like it before, and the file is one of the most important in the
> system.  Furthermore, the user does not have a recent backup because his
> tape drive failed and he was in the process of getting a new one.

Gotta hate timing like that.

Try an fsck on the relevant partition.

mark->
-- 
"Moral cowardice will surely be written as the cause on the death
certificate of what used to be Western Civilization." --James P. Hogan