Exit status values

Contributors netapp-ivanad akseldavis Download PDF of this page

Each exit status value has an error name, and the type associated with it. View the table to learn about the exit status value, error name, the type, and the description.

The following table contains information about exit status values. The exit status values are numbered sequentially. If SnapDrive for UNIX does not currently implement an error, that exit status value is not included in the table. As a result, there can be some gaps in the numbers.

Exit value Error name Type Description

1

Not supported

Command error

A function was invoked that is not supported in this version of SnapDrive for UNIX.

2

No memory

Fatal

The system has run out of memory. SnapDrive for UNIX cannot proceed until you free enough memory for it to work. Check other applications running to verify that they are not consuming excessive memory.

3

Invalid command

Command error

You issued an invalid command; this is likely to be a syntax error in the text of the command you entered.

4

Already exists

Command error

You requested that something be created that already exists. Usually, this error refers to a Snapshot copy name, which must not exist on the storage system volume where you are taking the Snapshot copy.

5

Create thread failed

Admin error

SnapDrive for UNIX could not create a process thread. Check the other processes running on the system to make sure that enough thread resources are available.

6

Not found

Command error

You included a file, data group, host volume, file system, or other argument on the SnapDrive for UNIX command line that does not exist.

7

Not a mounted file system

Command error

The file system you want to access either is not a valid file system or is not mounted.

9

Volume manager error

Command error

An error was returned when accessing the volume manager. See the specific error message to get details of which error, and why.

10

Invalid name

Command error

You supplied a name on the command line that was not correctly formatted.

For example, a storage system volume was not specified as filer:/vol/vol_name. This message also occurs when an invalid character is given in either a storage system or a volume manager based name.

11

Device not found

Admin error

SnapDrive for UNIX cannot access a LUN in the disk group that you want to take a Snapshot copy of.

Check the status of all LUNs, both on the host and on the storage system. Also check that the storage system volume is online, and that the storage system is up and connected to the host.

12

Busy

Command error

The LUN device, file, directory, disk group, host volume, or other entity is busy.

This is generally a nonfatal error that goes away when you retry the command. It sometimes indicates that a resource or process is hung, causing the object to be busy and unavailable for SnapDrive for UNIX to use.

It could also indicate you are trying to make a Snapshot copy during a period when the I/O traffic is too heavy for the Snapshot copy to be made successfully.

13

Unable to initialize

Fatal

SnapDrive for UNIX could not initialize third-party material that it needs. This can refer to file systems, volume managers, host cluster software, multipathing software, and so on.

14

SnapDrive busy

SnapDrive busy

Another user or process is performing an operation on the same hosts or storage systems at the same time that you asked SnapDrive for UNIX to perform an operation. Retry your operation.

Occasionally this message means that the other process is hung and you must kill it.

The Snapshot restore operation can take a long time under some circumstances. Be sure that the process you think is hung is not just waiting for a Snapshot restore operation to be completed.

15

Config file error

Fatal

The snapdrive.conf file has invalid, inadequate, or inconsistent entries. See the specific error message for details. You must correct this file before SnapDrive for UNIX can continue.

17

Bad permissions

Command error

You do not have permission to execute this command. You must be logged in as root to run SnapDrive for UNIX.

18

No filer

Admin error

SnapDrive for UNIX cannot contact the storage system needed for this command. Check the connectivity to the storage system indicated in the error message.

19

Bad filer login

Admin error

SnapDrive for UNIX cannot log in to the storage system using the login information you supplied.

20

Bad license

Admin error

A service SnapDrive for UNIX requires is not licensed to run on this storage system.

22

Cannot freeze fs

Admin error

A Snapshot create operation failed because SnapDrive for UNIX could not freeze the file systems specified in order to make the Snapshot copy. Confirm that the system I/O traffic is light enough to freeze the file system and then retry the command.

27

Inconsistent Snapshot copy

Admin error

The Snapshot restore operation failed because you requested a restore from a Snapshot copy with inconsistent images of the disk group. Inconsistent images can occur in the following cases:

  • You did not make the Snapshot copy using SnapDrive for UNIX.

  • The Snapshot create operation was interrupted before it set consistent bits, and thus, could not clean up (as in the case of a catastrophic system failure).

  • Some type of data problem occurred with the Snapshot copy after it was made.

28

HBA failure

Admin error

SnapDrive for UNIX encountered an error while trying to retrieve information from the HBA.

29

Bad metadata

Admin error

SnapDrive for UNIX encountered an error in the Snapshot copy metadata that it wrote when it created the Snapshot copy.

30

No Snapshot copy metadata

Admin error

SnapDrive for UNIX cannot perform a Snapshot restore operation because the metadata does not contain all requested disk groups.

31

Bad password file

Admin error

The password file has a bad entry. Use the snapdrive config delete command to delete the login entry for this storage system. Then reenter the login information using the snapdrive config set user_name command.

33

No password file entry

Admin error

The password file has no entry for this storage system. Run the snapdrive config set username filername command for every storage system on which you need to run SnapDrive for UNIX. Then try this operation again.

34

Not a NetAPPLUN

Admin error

A SnapDrive for UNIX command encountered a LUN that is not on a NetApp storage system.

35

User aborted

Admin error

The system displayed a prompt asking you to confirm an operation and you indicated that you did not want the operation performed.

36

I/O stream error

Admin error

The system input or system output routines returned an error that SnapDrive for UNIX did not understand.

Run snapdrive.dc and send that information to NetApp technical support so that they can help you determine which steps to perform to complete the recovery.

37

File system full

Admin error

An attempt to write a file failed because there was insufficient space on the file system. SnapDrive for UNIX can proceed when you free enough space on the appropriate file system.

38

File error

Admin error

An I/O error occurred when SnapDrive for UNIX was reading or writing a system configuration file or a temporary file.

39

Duplicate diskgroup

Command error

SnapDrive for UNIX got a duplicate minor node number when trying to activate a disk group.

40

File system thaw failed.

Admin error

A snap create command failed due to system activity on the file system. This usually occurs when the SnapDrive for UNIX file system freeze, required for the Snapshot copy, times out before the Snapshot copy is complete.

43

Name already in use

Command error

SnapDrive for UNIX attempted to create a disk group, host volume, file system or LUN but the name was already in use. To correct, select a name that is not in use, and re-enter the SnapDrive for UNIX command.

44

File system manager error

Fatal

SnapDrive for UNIX encountered an unexpected error from the file system when:

  • attempting to create the file system

  • making an entry in the file system mount table to automatically mount the file system at boot.

The text of the error message displayed with this code describes the error that the file system encountered. Record the message, and send it to NetApp technical support so that they can help you determine which steps to perform to complete the recovery.

45

Mountpoint error

Admin error

The file system mountpoint appeared in the system mount table file. To correct, select a mountpoint that is not in use or listed in the mount table, and re-enter the SnapDrive for UNIX command.

46

LUN not found

Command error

A SnapDrive for UNIX command attempted to access a LUN that did not exist on the storage system.

To correct, check that the LUN exists and that the name of the LUN is entered correctly.

47

Initiator group not found

Admin error

A storage system initiator group could not be accessed as expected. As a result, SnapDrive for UNIX cannot complete the current operation.

The specific error message describes the problem and the steps you need to perform to resolve it. Fix the problem and then repeat the command.

48

Object offline

Admin error

SnapDrive for UNIX attempted to access an object (such as a volume) but failed because the object was offline.

49

Conflicting entity

Command error

SnapDrive for UNIX attempted to create an igroup, but encountered an igroup of the same name.

50

Cleanup error

Fatal

SnapDrive for UNIX encountered an item that should be removed but is still there.

51

Disk group ID conflict

Command error

A snapdrive snap connect command requested a disk group ID that conflicts with an existing disk group.

This usually means that a snapdrive snap connect command on an originating host is being attempted on a system that does not support it. To fix this problem, attempt the operation from a different host.

52

LUN not mapped to any host

Admin error

A LUN is not mapped to any host. In other words, it does not belong to a storage system initiator group. To be accessible, the LUN must be mapped to the current host outside SnapDrive for UNIX.

53

LUN not mapped to local host

Admin error

A LUN is not mapped to the current host. In other words, it does not belong to a storage system initiator group that includes initiators from the current host. To be accessible, the LUN must be mapped to the current host outside SnapDrive for UNIX.

54

LUN is mapped using foreign igroup

Admin error

A LUN is mapped using a foreign storage system initiator group. In other words, it belongs to a storage system igroup containing only initiators not found on the local host.

As a result, SnapDrive for UNIX cannot delete the LUN.

To use SnapDrive for UNIX to delete a LUN, the LUN must belong only to local igroups; that is, igroups containing only initiators found on the local host.

55

LUN is mapped using mixed igroup

Admin error

A LUN is mapped using a mixed storage system initiator group. In other words, it belongs to a storage system igroup containing both initiators found on the local host and initiators not found there.

As a result, SnapDrive for UNIX cannot disconnect the LUN.

To use SnapDrive for UNIX to disconnect a LUN, the LUN must belong only to local igroups or foreign igroups; not mixed igroups. (Local igroups contain only initiators found on the local host; foreign igroups contain initiators not found on the local host.)

56

Snapshot copy restore failed

Admin error

SnapDrive for UNIX attempted a Snapshot restore operation, but it failed without restoring any LUNs in the Snapshot copy.

The specific error message describes the problem and the steps you need to perform to resolve it. Fix the problem and then repeat the command.

58

Host reboot needed

Admin error

The host operating system requires a reboot in order to update internal data. SnapDrive for UNIX has prepared the host for this update, but cannot complete the current operation.

Reboot the host and then re-enter the SnapDrive for UNIX command line that caused this message to appear. After the reboot, the operation will be able to complete.

59

Host, LUN preparation needed

Admin error

The host operating system requires an update to internal data in order to complete the current operation. This update is required to allow a new LUN to be created.

SnapDrive for UNIX cannot perform the update, because automatic host preparation for provisioning has been disabled because the snapdrive.conf variable enable-implicit-host-preparation is set to “off”.

With automatic host preparation disabled, you should use either the snapdrive config prepare luns command to prepare the host to provision LUNs or perform the preparation steps manually.

To avoid this error message, set the enable-implicit-host-preparation value to “on” in the snapdrive.conf file.

62

Not empty

Command error

An error occurred because SnapDrive for UNIX could not remove a storage system volume or directory. This may happen when another user or another process creates a file at exactly the same time and in the same directory that SnapDrive tries to delete. To avoid this error, make sure that only one user works with the storage system volume at the time.

63

Timeout expired

Command error

An error occurred because SnapDrive for UNIX could not restore a LUN within the time-out period of 50 minutes.

Record the message, and send it to NetApp technical support so that they can help you determine which steps to perform to complete the recovery.

64

Service not running

Admin error

An error occurred because a SnapDrive for UNIX command specified an NFS entity and the storage system was not running the NFS service.

126

Unknown error

Admin error

An unknown error occurred that might be serious. Run the snapdrive.dc utility and send its results to NetApp technical support for analysis.

127

Internal error

Fatal

A SnapDrive for UNIX internal error occurred. Run the snapdrive.dc and send its results to NetApp technical support for analysis.