I know it is something to do with customised attributes , duh
I had a corrupt volume group whose entry in the ODM had got corrupt and was deleting all the entries for it and its dependencies from CuAt, DuDv et al.
At the end, the volume group no longer appeared in a lsvg but an lsvg -o was still giving me an error with a message like vgid <long number> not found . The only remnant I could find of it in /etc/objrepos was in the CuAt.vc file which is not a normal odm file so was wanting to know what was being held in this file; e.g. is it a file holding details of opn stuff or similar and would it all be fixed by a reboot , or was there something else I needed to do.
As it happens, a reboot did fix it.
frank: hardly likely to get fired over it; to start with I did take a copy of /etc/objrepos and save it before starting, so wasnt likely to be the end of the world.
for interest, does anyone know what the CuAt.vc file is specifically for?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.