Dialog Box Warning Messages

DiskSuite displays the following messages in Warning Dialog Boxes. When these messages are displayed you can either continue or undo the action. The information here will help you determine which action to select.

All of the state database replicas are on the same controller.

You have populated the MetaDB template with slices that are all attached to the same controller. If the controller fails, you will not have access to any of the metadevices.

The new Concat/Stripe device dn has a slice with a mounted file
system. If an entry for its file system exists in
"/etc/vfstab" it will be updated when the Concat/Stripe is
committed so that the next mount of the file system will use the
new device. The system must be rebooted for this device mount to
take effect.

You have tried to add a slice that contains a mounted file system to a Concat/Stripe template. The slice that contains the mounted file system must be the first slice added. You cannot add a mounted file system to a RAID device.

Metadevice device_type dn will be deleted.
Data could be lost.
Really delete it?

This message displays when you attempt to delete any committed metadevice. You should continue only if you are sure your data is protected.

Stripe component dn is not the same size as component
dn. Extra space on the larger component will be wasted.

You have tried to add slices to a Concat/Stripe (stripe) that are a different size than the slices already in the stripe. Adding slices of a different sizes to a stripe causes wasted space.

Slice dn is on the same controller as slice dn.It is not advisable
to have slices from multiple submirrors on the same controller.

You have tried to create a Mirror with submirrors that are made up of slices attached to the same controller. If the controller fails, the mirror will not protect against lost data.

Slice dn is on the same disk as slice dn.It is not advisable to
have slices from multiple submirrors on the same disk.

You have tried to create a Mirror with submirrors that are made up of slices from the same disk. If the disk fails, the mirror will not protect against lost data.

Submirror dn is not the same size as submirror dn.
Extra space on the larger submirror will be wasted.

You have tried to create a Mirror that has differently sized submirrors. The extra space on the larger submirror cannot be used.

Submirror dn has an erred component.
Its data will not be valid after it is detached.

You have tried to detach or offline a submirror that has a slice reporting errors.

The file system mounted on metadevice dn has
been unmounted since the last status update.

You have tried to delete a metadevice that was unmounted. The device does not display the unmounted information. Select Rescan Configuration from the Metadevice Editor window's File menu to update this information.

The following components are in the erred state: dn
You may not replace RAID component dn until they are fixed.

You are replacing a component of a RAID metadevice that has reported errors (in the last-errored state). This cannot be performed if there are any other components in the RAID metadevice that have reported errors.

The following components are in the erred state: dn
The data for the component replacing RAID component dn may be
compromised.

You are replacing or enabling a RAID component that has reported errors. This action is dangerous if there is another component that has reported errors (in the last-errored state). The data on the new component may not be completely accurate.

The following components are in the last_erred state: dn
The data for RAID component dn may be compromised.

You are replacing or enabling a RAID component that is reporting errors. This action is dangerous if there is another component that has reported errors (in the last-errored state). The data on the new component may not be completely accurate.

The following components have erred: dn
The data for RAID component dn WILL NOT BE RESYNCED.

You have tried to replace a component in a RAID metadevice and there are two or more components reporting errors. It is not possible to replace the components because there is no way to recreate the data. If you proceed with the replacement, you must obtain the data from a backup copy.

The format of disk dn has changed.
You must restart metatool to incorporate the changes.

You have reformatted a disk that used to have a metadevice, file system, or database replica and selected the Rescan Configuration option from the Metadevice Editor window's File menu. If the disk is not being used, the new information is read by DiskSuite and displayed in the appropriate windows (for example, Slice Browser and Disk View).

The log device for Trans dn cannot be detached until
the Trans is unmounted or the system is rebooted.

You have tried to detach a log and commit the Trans object. The detach will not be performed as long as the log master is mounted. The Trans device is actually in a "detach pending state."

The master device dn for Trans dn has a mounted file system.

In order for logging of
this file system to be activated, the file
/etc/vfstab must be updated with the
new device name and the system rebooted.

Committing Trans dn will update
/etc/vfstab automatically if an entry exists
for the file system.

You have tried to add a metadevice that has a mounted file system to a Trans master. DiskSuite will automatically change the entry for the file system in the /etc/vfstab file. If an entry for the file system does not exist in the /etc/vfstab file, you must create one. The message also tells you to reboot the system.

The master device dn for Trans dn has a mounted file system.

If an entry for its file system exists in "/etc/vfstab," it will
be updated with the new device to mount for the file system.

The system must be rebooted for this
device mount to take effect.

You have tried to add a master device that has a mounted file system to a Trans. DiskSuite will automatically change the entry for the file system in the /etc/vfstab file. If an entry for the file system does not exist in the /etc/vfstab file, you must create one. The message also tells you to reboot the system.

The metadevice dn has been removed as a swap device
since the last status update.

You have tried to delete a device that is the swap device. The device still says it is swap. To update the device's status, select Rescan Configuration from the Metadevice Editor window's File menu.

The new Mirror device dn
has a submirror with a mounted file system.

If an entry for its file system exists in /etc/vfstab, it will
be updated with the new device to mount for the file system.

The system must be rebooted for this
device mount to take effect.

You have tried to add a Concat/Stripe that has a mounted file system to a Mirror. DiskSuite will automatically change the entry for the file system in the /etc/vfstab file. If an entry for the file system does not exist in the /etc/vfstab file, you must create one. The message also tells you to reboot the system.

The state database will have no replicas.
If the system reboots, all metadevices will
be corrupted.

You have tried to remove the state database and all replicas from the MetaDB template. If you commit, you will not have access to any metadevices after the next reboot.

The submirror dn has a slice with a mounted
file system.

In order for mirroring of
this file system to be activated, the file
/etc/vfstab must be updated with the
new device name and the system rebooted.

Committing Mirror dn will update
/etc/vfstab automatically if an entry exists
for the file system.

You have tried to add a submirror that has a mounted file system to a Mirror. DiskSuite will automatically change the entry for the file system in the /etc/vfstab file. If an entry for the file system does not exist in the /etc/vfstab file, you must create one. The message also tells you to reboot the system.

This log is not mirrored. It is recommended that you mirror logs
whenever possible to avoid single points of failure.

You have tried to create a Trans device with a log that is not mirrored. If the log is not mirrored, the data could be lost or unavailable.

Trans dn has no log device.

You have tried to commit a Trans device that has no Trans log. You should add the log before committing the device. Until you add the log, the logging feature is disabled.