15.7 Junctions Are Broken After a Volume Object Update

In very rare cases, it is possible that a volume’s DFS GUID for a volume needs to be regenerated after a Volume object is updated, causing junctions that point to the volume to be broken.

For NSS volumes, the DFS GUID for a volume is stored as an attribute of the Volume object and in the ~DFSINFO.8-P file in the root directory of the volume. If the old Volume object and the ~DFSINFO.8-P file are not present when you perform the Update eDirectory option for an NSS pool or volume, then the Volume object is created without a DFS GUID.

If junctions are broken after updating a Volume object, run a VLDB repair or add an entry (available on Linux only) to the VLDB to generate a DFS GUID for the volume. Afterwards, you must delete and re-create the junctions that point to the volume so the junctions can pick up the volume’s new DFS GUID.