> Hi All,
>
> Has anyone else experienced a situation where mountpoints got scrambeled?
>
> - I cannot traverse them (file does not exist)
> - fs rmm does not work
> - fs mkm says it allready exist
> - rm obviously does not work (it is a diectory)
> - rmdir does not work (it is *not* a directory)
>
> I'm stuck. How did this happened? The whole cell is *not* affected; it's "only"
> the place where all the binaries reside, so noone can start their apps.
> It's not related to one specific server, RO copies are on different servers
> of different architechtures. What's puzzling is that it's only the apps
> volumes...
>
> - I *am* able to create a new mountpoint with a new name reusing the old
> volumes, so volumes seems ok.
>
> What happened to my mountpoints? (it worked yesterday)
> It is the volume containing the mountpoint that are hurt?
>
> Any clues for a work-a-round?
>
> Thanks,
> /peo
>
>
> [EMAIL PROTECTED]
>
>
Peo,
I have seen that problem before. I can only assume that the inode got screwed
up on it. The only way I could get rid of it was to create a new volume and do
a cp -Rp. Then just do a fs mkm. You can't do a vos dump because it will show
up in the new volume.
Cyd
