"bad file number" errors 1

[ravashaak]

I have a client that is experiencing "bad file number" errors in the savegroup completion reports. In the past, this almost always indicated an issue with the filesystem in question. What I would like to know is exactly what this error means (if anyone knows). Or is it a fairly generic disk/filesystem error?

I've noticed that in this instance of the error, that the particular directory in question has absolutely no contents, not even a "." or "..", which is a bad thing. Is the bad file number error an indication of having zero contents in a directory? If so, can it also indicate other errors?

Thanks

 

[605]

There is no straight translation as this message can appear under different
situations during a read or write process. Obviously in your case,
it points to the fact that the underlaying program, uasm, will not be
able to read the filesystem.

The input that your directory seems to be "incomplete" is in fact a
very good one. You may try to fix it using the OS repair utilities.

 

[ravashaak]

Thanks for confirming my suspicions regarding this type of error. And we did recover the directories in question. I suspect some of the raid hardware to be causing this issue, but only time will tell.