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:

• Notice log messages

• Warning log messages

• Panic log messages

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:

• dev is a device name.

• dnum is a metadevice name.

• num is a number.

• state is a Trans device state.

• trans is either "logging" or "master."

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).