test

Solstice DiskSuite 4.2.1 Reference Guide

DiskSuite Tool Messages

This part of this appendix contains the status, error, and log messages displayed by DiskSuite's graphical user interface, DiskSuite Tool.

State Information Terms

The dialog boxes shown in DiskSuite Tool use the following terms when the state of the components is reported.

Metadevice Editor Messages

The Metadevice Editor has a message line at the bottom of the window that displays information about objects and actions. There are two types of feedback displayed:

Dialog Box Error Messages

DiskSuite displays the following messages in Error dialog boxes. When these messages are displayed, the only choice on the dialog box is OK. The action you attempted will not be performed. Use the information here to correct the error. 


A RAID can only have one operation that causes a resync per commit

You have tried to commit two separate changes to a RAID device at the same time. While the changes may be valid, only one can be performed at a time. For example, if you replace a slice and add a new slice, this message is displayed. You must perform one change and click on the Commit button, then perform the other change and click on the Commit button.


Concat dn has no stripes

You have tried to commit a concatenation that has no stripes. You must add stripes to the concatenation.


You cannot delete a metadevice that is in use.

You have tried to delete a metadevice that contains a mounted file system, is being swapped on, or is open as a raw device.


dn has no components.

You have tried to commit a Concat/Stripe template that has no slices. You must add slices to the object before clicking on the Commit button.


Mirror dn has no submirrors

You have tried to commit a mirror that has no submirrors. You must add submirrors before clicking on Commit.


RAID dn must have at least three slices.

You have tried to commit a RAID metadevice that has fewer than three slices. Add the necessary slices and commit the RAID metadevice.


Slices added to a RAID device must be at least
as large as the smallest original slice.

You have tried to add a slice to a RAID device that is smaller than the slices that are already part of the RAID device.


Slice slice is mounted. You cannot add it to Concat/Stripe dn, it
is not the first mounted slice to be added.

You have tried to add a slice that has a mounted file system to a Concat/Stripe and there is already at least one slice in the Concat/Stripe. The slice with the mounted file system must be the first one added to the Concat/Stripe.


Slice slice is mounted. You cannot add it to dn, it already has a
mounted slice.

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.


Slice slice is mounted. You cannot add a mounted slice to a RAID
device, doing so would corrupt the file system.

You have tried to add a slice that contains a mounted file system to a RAID template. Choose another slice that does not contain any data.


Slice slice is too small to be used in a RAID device.

You have tried to add a slice that is too small. The slice being added is either smaller than the slices already in the RAID device or is too small to be used in a RAID device.


Submirror dn has a mounted file system, it should be the first
submirror added.

You have tried to add a submirror that contains a mounted file system to an existing mirror. To mirror this file system, create a one-way mirror using this submirror then attach another submirror that does not contain data.


Submirror dn is too small.

You have tried to add a new submirror that is smaller than the current size of the Mirror. The submirror must be as large as the existing submirror.


Mirror dn has a component with a file system mounted. You cannot
add another submirror.

You have tried to add a submirror that contains a mounted file system and the Mirror already has a mounted file system on the other submirror. You must add an unassigned slice.


The root file system may not be mounted on
a concat with more than one stripe.

You have tried to drop the slice that contains the root file system into a Concat/Stripe template. Remove one of the existing stripes.


The root file system may not be mounted on a trans device.

You have tried to drop the slice that contains the root file system into a Trans device template. The root file system cannot be placed in a Trans device.


Trans dn has no master

You have tried to commit a Trans device that has no master device. Add the master device and commit the device.


You cannot add device to a RAID device while it is initializing

You have tried to add a slice or hot spare pool to a RAID device that has been committed and is initializing. Wait until the device is initialized. 


You cannot replace a slice in a RAID device while it is
initializing.

You have tried to add a slice to a RAID device that has been committed and is initializing. Wait until the device is initialized.


The value you entered value is too large.
You should use a value less than new value, which is the
maximum possible device size.

You tried to enter an unacceptably large value in one of the Slice Filter window`s size fields.


Your attempt to change the name of Hot Spare Pool hspnnn
to hspnnn failed for the following reason:

You tried to change the name of a hot spare pool to a name that already exists, or the name is not valid.


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

You tried to add a slice to a RAID5 metadevice that is not the same size as the existing slices in the RAID device.


You cannot change the hot spare pool for a RAID device while it
is initializing.

You tried to change the current hot spare pool for a RAID5 metadevice during its initialization. Wait for the initialization to complete before attempting to change the hot spare pool again.


The RAID device has failed to initialize. It cannot be repaired
and should be deleted.

There was an error when trying to initialize the RAID5 metadevice. The only recourse left is to delete the device and recreate it, after repairing any errored slices.


A slice in a created stripe may not be replaced unless the stripe
is part of a submirror with redundancy.

You can only replace a slices if data redundancy exists.


A slice in a stripe may not be enabled unless the stripe is part
of a submirror with redundancy.

You can only enable slices if data redundancy exists.


The metadevice state database has not been committed since slice
slice was added. You cannot restore replicas on the slice.

You need to commit the MetaDB object before enabling any broken slices.


There is no device with a mounted file system which matches
the path name path.

You tried to drag a file name from Storage Manager to the Metadevice Editor canvas and DiskSuite Tool could not locate the device containing the file system.


Disk Set Released
host no longer owns the setname disk set.
setname cannot continue; you must exit.
 


Disk Set Changed
An external change has occurred to the setname disk set.
 


Disk Set Load Failed
Unable to load disk set setname.

The above three messages indicate that changes were made to the diskset from the command line while DiskSuite Tool was running on that diskset.


Statistics sheets are not available for controllers, trays or
slices.

You tried to display the Device Statistics window for a controller, tray, or slice. The Device Statistics window is only available for metadevices or disks.


Sync NVRAM is only available for SPARCstorage Array controllers,
trays and disks with working batteries.

You tried to sync NVRAM on a non-SPARCstorage Array device, or you tried to sync NVRAM on a SPARCstorage Array whose battery has failed.


Fast Write is only available for SPARCstorage Array controllers,
trays and disks with working batteries.

You tried to enable Fast Write on a SPARCstorage Array device whose battery has failed.


Reserve Disks is only available for SPARCstorage Array
controllers, trays and disks.

You tried to perform a disk reservation on a non-SPARCstorage Array device.


Release Disks is only available for SPARCstorage Array
controllers, trays and disks.

You tried to release a disk reservation on a non-SPARCstorage Array device.


Start Disks is not available for slices.

Slices by themselves cannot be started, only disks.


Stop Disks is not available for slices.

Slices by themselves cannot be stopped, only disks.


You may not detach a submirror while it is resyncing.

You cannot detach a submirror in the process of resyncing.


Error while trying to reserve lock for metaset setname.

The lock for setname could not be acquired. Either another instance of DiskSuite Tool or the command line currently has the lock.


Interlace value is out of range.

You entered an invalid interlace value for the striped metadevice or RAID5 metadevice.


Failed trying to exchange metadevices dn and dn.

You cannot exchange metadevice names of a metadevice that is in use.


Failure trying to rename dn to dn.

You cannot rename a metadevice that is in-use, nor can you rename a metadevice to a name that already exists.


Metadevice name not in range dn - dn.

You tried to give a name to a metadevice outside the current defined range. If necessary, increase the value of nmd in the /kernel/drv/md.conf file.


The hot spare pool name not in the range hsp000 - hsp999.

Hot spare pools must be named hspnnn, where nnn is a number between 000 and 999.


The hot spare pool hspnnn already exists.

You tried to create a hot spare pool with an existing hot spare pool's name.


You cannot delete a mounted trans device that has an attached
logging device.

To delete a trans metadevice, first detach the logging device.


The metadevice dn is currently either opened, swapped on, or
mounted. Deleting it will cause the name to be pushed down.

The mirror or trans metadevice you are trying to delete is currently in-use. The deleted device name will be switched with one of its subdevices names. In the case of a mirror, the mirror name is switched with one of its submirror names. In the case of a trans metadevice, the trans name and the master device name are switched.


You cannot delete a mounted mirror with more than one submirror.

To delete the mirror, make it into a one-way mirror.


You cannot delete a mounted trans device whose master is not a
metadevice.

You are attempting to delete a mounted trans device whose master device is a slice. Unmount the trans metadevice to be able to delete it.


Cannot purge the NVRAM for device. Disk is reserved by another host.

Cannot sync the NVRAM for device. Disk is reserved by another host.

Cannot reserve device. Disk is reserved by another host.

Cannot release device. Disk is reserved by another host.

Cannot start device. Disk is reserved by another host.

Cannot stop device. Disk is reserved by another host.

Cannot disable fast write for device. Disk is reserved by another
host.

Cannot enable fast write for device. Disk is reserved by another
host.

Cannot enable fast write for synchronous writes for device. Disk
is reserved by another host.

The above messages indicate that another host has a reservation on device. To perform the desired action, first release the reservation.


You cannot detach an existing submirror while a replace, enable
or attach is pending.

You tried to detach a submirror that is currently be replaced, enabled, or attached. Wait for the operation to complete before attempting the detach again.


You cannot enable a slice in a mirror while the mirror is
resyncing.

You tried to enable a slice in a submirror while the mirror is being resynced. Wait for the operation to complete before attempting the enable again.

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.

Dialog Box Information Messages

DiskSuite displays the following messages in information dialog boxes. These messages tell you a common mistake has been made or provide a helpful message. These dialog boxes appear with a large "i" on the left side of the message. There is only one button on the bottom of this dialog: OK. 


You added additional capacity to the metadevice metadevice_type on
which file system file_system is mounted. You have the
option of growing this file system to take advantage of
this additional space either now or later (by hand).
If you choose to grow it now, the application will be
disabled until the growth process completes.

The command that will be run is:

    "growfs -M file_system /dev/md/rdsk/dn"

Do you want to grow the metadevice now or later?

You have tried to add slices to a Concat/Stripe metadevice. Following a commit, you can expand the file system, as documented in the Solstice DiskSuite 4.2.1 User's Guide.


The file system file_system mounted on metadevice dn
is now being grown.

You are growing a file system. 


Statistic sheets are not available for the Metastate
database (metadb), Hot Spare Pools or slices.

You cannot display a Device Statistics window for the metadevice state database, hot spare pools, or slices.

Metadevice Editor Window Messages

The following messages are displayed when you are pointing to an object inside the Metadevice Editor window. An explanation of the message follows the sample output. 


Click or drag to create a new object device

You are pointing at any of the five Template icons. object is either Trans, RAID, Mirror, Concat/Stripe, or Hot Spare Pool. 


component_type dn: size=size, use=use, status=status

You are pointing at an object (component_type) on the canvas. The component_type is either Trans, RAID, Mirror, Concat/Stripe, or Hot Spare. The metadevice name is reported as dn, where the default size for n is a number in the range 0 to 127. The size is the capacity of the metadevice (for example, 500 Mbytes). The use is either Unassigned, Submirror, or /filesystem. The status is reported as OK, Attention, Urgent, or Critical.


Drag objects into this work area to look at or modify them...

You are pointing at an empty canvas or the device list in the Metadevice Editor window. 


hspnnn: status=status

You are pointing at a Hot Spare Pool on the canvas. The Hot Spare Pool name is reported as hspnnn, where nnn is a number in the range 000 to 999. The status is reported as OK, Attention, Urgent, or Critical.


Slice cntndnsn: size=size, use=use, status=status

You are pointing at a disk slice on the canvas. The name of the slice appears in the format, cntndnsn. The size is the capacity of the slice (for example, 5 Mbytes). The use is either Unassigned or Component. The status is reported as OK, Attention, Urgent, or Critical.


Use Button2 to pan the viewport over the work area ...

You are pointing at the Panner. By pressing the middle button and moving the cursor, you move the canvas to a new view area.

Messages Displayed When Dragging an Object

The following messages are displayed when you are dragging an object inside the Metadevice Editor window. An explanation of the message follows the sample output. 


Concatenations must be part of a mirror
for hot spare pools to function

You are dragging a Hot Spare Pool over a concatenation. This message is telling you that the Concat/Stripe must be part of a Mirror or the Hot Spare Pool you are dropping will not work.


Drop a concatenation into mirror dn

You are dragging a Concat/Stripe over the specified Mirror. If you drop the Concat/Stripe, it will become part of that Mirror.


Drop a concatenation to replace submirror dn

You are dragging a Concat/Stripe over the specified submirror. Drop the Concat/Stripe inside the rectangle that contains the submirror to make the replacement.


Drop a hot spare pool to assign it to concatenation dn

You are dragging a Hot Spare Pool over the specified concatenation. By dropping the Hot Spare Pool into the Concat/Stripe, it becomes associated with that concatenation.


Drop here to associate a hot spare pool with this RAID

You are dragging a Hot Spare Pool over the specified RAID device. If you drop the Hot Spare Pool, it will become associated with the RAID device.


Drop a metadevice or slice into trans log

You are dragging a metadevice or slice over a Trans device. If you drop the metadevice or slice, it will become part of the Trans device.


Drop a metadevice or slice into master

You are dragging a metadevice or slice over the Master of a Trans device. Drop the object into the Master to add it to the device.


Drop a slice into hot spare pool dn

You are dragging a slice over the specified Hot Spare Pool. Drop the slice to add it to the Hot Spare Pool.


Drop a slice into RAID dn

You are dragging an unused slice over the specified RAID device. If you drop the slice, it will become part of the RAID device.


Drop a slice of the same size to replace the current slice

You are dragging a slice either over a committed RAID device or over a submirror that has more than one submirror. You can drop the new slice on the existing slice to make a replacement.


Drop a slice to replace current slice

You are dragging an unused slice over a Concat/Stripe, RAID, or Trans device. To replace the slice you are over, release the middle button and drop the slice. 


Drop a slice into stripe dn or commit

You are dragging an unused slice over a Concat/Stripe that has one or more slices. You can populate the Concat/Stripe with additional slices or select the Concat/Stripe (stripe) and execute a commit.


Drop a slice to add new replicas; you should have at least
three replicas.

You are dragging a slice over the MetaDB object. Drop the slice to create another replica. DiskSuite requires the configuration have a minimum of three slices in the MetaDB object.


Drop at least one concatenation into mirror dn

You are dragging a Concat/Stripe over the specified Mirror. You must drop a minimum of one Concat/Stripe into the specified Mirror.


Drop at least one slice into stripe dn

You are dragging an unused slice over a Concat/Stripe that has zero slices. You must populate the Concat/Stripe (stripe) with a minimum of one slice.


Drop at least three to create the RAID parity group

You are dragging an unused slice over the specified RAID device. You must drop a minimum of three slices into the RAID device.


Drop a slice to add a new replica.

You are dragging a slice over the MetaDB object. Drop the slice to create another replica.


You cannot add more concatenations;
mirror dn already has three submirrors

You are dragging a Concat/Stripe over the specified Mirror. You cannot add another Concat/Stripe (submirror) to a Mirror that already has three submirrors.


You cannot add slices to committed stripe dn

You are dragging an unused slice over a committed Concat/Stripe. DiskSuite does not permit you to add slices to a committed Concat/Stripe (stripe).


You cannot replace in-use slices in a hot spare pool

You are dragging an unused slice over a slice that is in use in a committed Hot Spare Pool. You cannot drop the new slice on a slice in a Hot Spare Pool that is currently in use.


You cannot replace objects in committed RAID dn

You are dragging an object over the specified RAID device. Because the device is committed, you cannot make replacements.


You cannot replace slices in a committed stripe unless
it is part of a submirror

You are dragging a slice over a a committed Concat/Stripe. You cannot make changes to this metadevice, unless it is part of a submirror.


You cannot replace submirror dn when
mirror dn has only one submirror

You are dragging a submirror over the specified submirror. You cannot drop the submirror into the Mirror when there is only one submirror present.


You cannot replace slices in a committed trans device

You are dragging an unused slice over a slice that is in use as a Trans master or log. You cannot replace slices in a committed Trans device.

Disk View Window Messages

The Disk View window has a message line at the bottom that displays information about objects and actions. There are two types of message line feedback displayed:

Messages Displayed When Pointing at an Object

The following messages are displayed when you are pointing to an object inside the Disk View window: 


Slice cntndnsn: size=size, use=use, status=status

You are pointing at a disk slice on the canvas. The name of the slice appears in the format, cntndnsn. The size is the capacity of the slice (for example, 5 Mbytes). The use is either Unassigned, Component, Hot Spare, MetaDB Replica, Reserve, mount_point, swap, Trans Log, or Overlap. The status is reported as OK, Attention, Urgent, or Critical.

Messages Displayed When Dragging an Object

The following messages are displayed when you are dragging an object inside the Disk View window. 


Drag slices onto object templates in the metadevice editor canvas

You are dragging an object from the Disk View window. You can drop the slices inside an object or on the canvas of the Metadevice Editor window.

Log Messages

Log messages are those passed by syslog(3) to the syslogd(1M). These messages are appended to a file and written to the console window. These messages will not appear in any DiskSuite error or problem list.

The log messages are divided into the following categories:

The log messages displayed by DiskSuite are listed in alphabetical order below. Each message is always preceded with md: The variables in these messages indicate the following:

Note -

When the initial portion of a message begins with a variable, the message is alphabetized by the first word following the variable.

Notice Log Messages 


Could not load misc /dev

The named misc module is not loadable. It is possibly missing, or something else has been copied over it.


db: Parsing error on `dev'

The set command in /etc/system for the mddb.bootlist<number> is not in the correct format. Run metadb -p to place the correct set commands into the /etc/system file. 


dnum: Hotspared device dev with dev

The first device name listed has been hot spare replaced with the second device name listed. 


dnum: Hotspared device dev(num, num) with dev(num, num)

The first device number listed has been hot spare replaced with the second device number listed. 


dnum: no mem for property dev

Memory could not be allocated in the prop_op entry point.

Warning Log Messages


dnum: not configurable, check /kernel/drv/md.conf

This error occurs when the number of metadevices as specified by the nmd parameter in the /kernel/drv/md.conf file is lower than the number of configured metadevices on the system. It can also occur if the md_nsets parameter for disksets is lower than the number of configured disksets on the system. To fix this problem, examine the md.conf file and increase the value of either nmd or md_nsets as needed.


dnum: Cannot load dev driver

The underlying named driver module is not loadable (for example, sd, id, or a third-party driver). This could indicate that the driver module has been removed.


Open error of hotspare dev
Open error of hotspare dev(num, num)

The named hot spare cannot be opened, or the underlying driver is not loadable.


dnum: read error on dev
dnum: write error on dev

A read or write error has occurred on the specified metadevice at the specified device name. This happens if any read or write errors occur on a metadevice.


dnum: read error on dev(num, num)
dnum: write error on dev(num, num)

A read or write error has occurred on the specified metadevice at the specified device number. This happens if any read or write errors occur on a metadevice.


dnum: read error on dnum
dnum: write error on dnum

A read or write error has occurred on the specified metadevice at the specified device number. This happens if any read or write errors occur on a metadevice.


State database commit failed
State database delete failed

These messages occur when there have been device errors on components where the state database replicas reside. These errors only occur when more than half of the replicas have had errors returned to them. For example, if you have three components with state database replicas and two of the components report errors, these errors may occur. The state database commit or delete is retried periodically. If a replica is added, the commit or delete will finish and the system will be operational. Otherwise, the system will time out and panic.


State database is stale

This message occurs when there are not enough usable replicas for the state database to be able to update records in the database. All accesses to the metadevice driver will fail. To fix this problem, add more replicas or delete inaccessible replicas.


trans device: read error on dnum
trans device: write error on dnum

A read or write error has occurred on the specified logging or master device at the specified metadevice. This happens if any read or write errors occur on a logging or master device.


trans device: read error on dev
trans device: write error on dev

A read or write error has occurred on the specified logging or master device at the specified device name. This happens if any read or write errors occur on a logging or master device.


trans device: read error on dev(num, num)
trans device: write error on dev(num, num)

A read or write error has occurred on the specified logging or master device at the specified device number. This happens if any read or write errors occur on a logging or master device.


logging device: dnum changed state to state
logging device: dev changed state to state
logging device: dev(num, num) changed state to state

The logging device and its associated master device(s) have changed to the specified state(s).

Panic Log Messages 


State database problem

A failed metadevice state database commit or deletion has been retried the default 100 times.


dnum: Unknown close type
dnum: Unknown open type

A metadevice is being opened/closed with an unknown open type (OTYP).