Removing data containers for derived objects

Learn how to remove data containers for derived objects.

The standard rm(1) command causes a shareable derived object to disappear from the dynamic view. The effect on physical data storage is as follows:

• If the data container of a DO is in the private storage area of a view, rm deletes that data container.
• If the data container of a DO is in a VOB storage pool, the data container is not affected.

In both cases, the derived object in the VOB database is not deleted. The only change to the derived object is that its reference count is decremented.

When a build overwrites a nonshareable or unshared DO, the MVFS removes the old data container from the private storage area of a dynamic view, and creates a new one there. It also creates a new CR. At the operating system level, the effect is that an existing file is overwritten.