Quick kudos to Dr. Tom Blinn for his fast response:
> What is the underlying file system? If it's UFS, then you need to fsck it, if
> it's AdvFS, then you need to run AdvFS verify on it. You MIGHT be able to
> work around it by moving the directory entry to another directory, and then
> remove the other directory. Or try "rm -f". Cleaning up file system errors
> when it's the metadata can be tricky.
Good old UNIX! It's always more involved than you want it to be...
I tried the "rm -f" with the same results. Also tried to "mv" an empty
file onto the name and got the "Bad file number" error again.
In fact, the filesystem is AdvFS and to make matters worse it is part of a
TruCluser disk service -- which means it becomes more difficult to umount
and verify. Ah, me; such is the life of a sysop. You'd think I would get
used to it after 25 years.
Thanks Dr. Tom! It's so good to have you watching over us and helping out!
--CHRis
Original message:
> I have a message coming out of Legato NSR during backups pointing to a
> particular file name and saying it has a "Bad file number". I presume
> this means the inode value in the directory does not point to a valid
> inode.
>
> If I try to "rm" this file, I get a "file not found" message.
>
> How do I eliminate this entry in the directory? For you former VMSers,
> what I want to do is the equivalent of a SET FILE/REMOVE.
-
=============================================================================
Chris H. Ruhnke Phone: (314)233-7314
IBM Global Services M/S S306-6340 FAX : (314)234-2262
325 J.S. McDonnell Blvd Email: Ruhnke_at_US.ibm.com
Hazelwood, MO 63042
Received on Fri Jul 23 1999 - 13:25:07 NZST