Re: fs corruption problem

[Julian Opificius <julianop mninter net>]

Alastair,
Thanks for your input.
The problem was that the entries had forward slashes in them, telling the 
system they were directories, yet rmdir didn't see them as valid, so nobody 
wanted to take responsibility for them.

Several runs through fsck (yeah, go figure) converted the "/" characters to 
"." characters, at which point it was easy to it get up an running.

Cheers to all who offered input.

j.
==============
At 09:38 AM 6/30/03, you wrote:
> Julian wrote:
>
> > Michael,
> > Yes, naturally I've tried all options of rm as documented in rm --help 
> > and man rm.
> > Also true of rmdir.
> > Yes I want to remove it because during the boot process I'm told there 
> > are bad characters in the file name.
> > The two rogue files was originally here:
> > /var/log/seti//dev/log
> > /var/log/seti//var/loc
> [...]
> > julian.
> > ============
>
> Julian,
>
> Check to see if there are any bad characters.  To do that, type this
>
>         cd /var/log/seti (or wherever the rouge files maybe)
>         ls -rQ *
>
>         (or)
>
>         ls -rb *
>
> This will give an indication if there are any non-visable controle 
> characters within the filename.
>
> If there are, try deleteing using the characters that you do see.
>
>         rm -i /dev/log*
>         rm -i /var/loc*
>
>
> --
> --Alistair
>
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request redhat com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list