KB Logo

TOLIS Group Knowledge Base

Browse KB by category:
Go to KB #:
Glossary
Email   Bookmark



BRU Messages - Understanding BRU Error Codes and the causes of BRU messages

Views: 35412
Votes: 6
Posted: 04 Jan, 2008

BRU Messages

Search Note: Use your browsers built-in search feature to search for the desired BRU Message.

All BRU messages are associated with a number. The message number consists of a single letter followed by three digits. The first letter of the message number indicates the type of message (i.e.: [I181] is an Informational Message). The messages are listed below:

A - alert message
BRU is alerting the user of a problem. This problem or alert, is not as strong as an error or a warning message but none the less BRU will require a response. This is message is usually followed by a “Q” message

E - error message
BRU has found that the current operation has errors that it can not overcome. Depending on the MAXERRORS setting in your BRUTAB, BRU will terminate with an execution summary exit code of 2.

I - informational message
Information regarding the current process. This type of message is echoed to the /var/log/bruexeclog file as an “L” message.

L - log message
Entry message to the /var/log/bruexeclog regarding the current process. Entry is a copy of what is sent to the screen with the “I” message. All entries are made with a date and time stamp.

Q - query message
BRU is waiting for a response to complete the current process.

W - warning message
BRU has found problems with the current operation. The errors where not serious but BRU was unable to resolve the issue. Depending on your setting for MAXWARNINGS in your BRUTAB file BRU will terminate the current process.

NOTE: You should investigate all WARNING and ERROR messages reported by BRU. These messages can result in you not being able to restore your data. Many BRU messages are the result of errors returned by the UNIX system. For these types of errors, the UNIX error message is included as part of the BRU message. This portion of the message is described below:

errno = code, description

code is the UNIX error number.
description is a brief text message associated with the error number. These are system values and are not BRU errors.  BRU simply reports them as they are defined by the system.


BRU Message Code Listing

[E001] specify mode (-cdeghitx)
The user ran BRU without specifying the mode. The user must specify a valid mode. See Appendix D for a list of BRU modes.

[W002] filename: can’t open archive: errno = code, description
BRU couldn’t open the archive file filename for some reason. The reason is indicated by the UNIX error message. Make sure that the device actually exists. Also see if another process (or an old BRU process) still has control of the device.

[W003] filename: warning - close error on archive: errno = code, description
BRU received an error from the operating system when BRU attempted to close the archive. The reason is indicated by the UNIX error message.

[W004] warning - archive read error at block blocknum: errno = code, description
BRU received an unrecoverable error when attempting to read an archive. The reason for the error is indicated by the UNIX error message. Whatever data was available at that location in the archive is unrecoverable.

[W005] warning - archive write error at block blocknum: errno = code, description
BRU received an unrecoverable write error while attempting to write an archive. The reason for the error is indicated by the UNIX error message. Whatever data that was to be written at that location in the archive has been discarded. Proper corrective action depends upon the situation and the specific file within which the error occurred. If this error occurred on the first block of an archive, the archive may be write protected, in which case, the wperr parameter is probably set incorrectly in the brutab file.
Another possibility is that the I/O buffer size is too large for the given device. Experiment with a smaller buffer size. Set the buffer size with the bufsize parameter in the brutab file or use the -b option to set it on the command line.

[E006] seek error on archive: errno = code, description
BRU received an unrecoverable seek error from the operating system on an archive file. The reason for the error is indicated by the UNIX error message. Make sure that your archive device actually has the capability to do random seeks to any location. Most tape drives do NOT have this capability. Check the value of the seek parameter in the brutab file. If your device does not have the ability to do random seeks, you must set seek=0.

[E007] media size smaller than I/O buffer size!
This error was caused when BRU detected a media size that was inconsistent with the I/O buffer size. The media size should be at least as large as the I/O buffer size. It is not possible to write to device if the media size smaller is smaller than the buffer size (i.e. BRU cannot write 1 megabyte of buffer data to a floppy with a media size of 720 kilobytes). Check the brutab file and make sure that the bufsize parameter is less than size.

[W008] warning - buffer size bufsize exceeds maximum maxbufsize allowed for device
Check the brutab file and make sure that bufsize is less than maxbufsize.

[E009] can’t allocate bufsize archive buffer: errno = code, description
This message was caused when BRU could not allocate an I/O buffer of the size requested. Try reducing the buffer size to a smaller value. This can be done with the -b command line option, or the bufsize parameter entry in the brutab file.

[W010] filename: warning - block sequence error
[E010] filename: warning - block sequence error

BRU detected an inconsistency in the ordering of blocks returned by the archive device on a read.
For example, BRU asked for blocks “11, 12, 13, 14, 15” and got blocks “11, 12, 14, 15, 16.” This error may indicate a hardware problem. If this message occurs at the start of the 2nd volume (when reading a multiple volume archive), it probably means that the last few blocks of the previous volume were missing or were unreadable. This can occur if the media size parameter was set too large in the brutab file (i.e. size=150M for a 60 megabyte tape) during the backup and BRU attempted to write past the end of the previous volume. With some tape drives, it may also occur if the media size was set to zero (unknown). The problem can usually be avoided by setting the media size to a value that is certain to be less than the maximum capacity of the volume (i.e. set size=149MT for a 150 megabyte tape).

To detect and avoid this problem, always verify your archive immediately after the backup is performed. AUTOSCAN does this automatically for all devices that have an entry in the brutab file (unless noautoscan is set or you are using a norewind device).

This was changed from a warning message (the leading "W") to an error message (the leading "E") in BRU 18.0.

[W011] warning - file synchronization error; attempting recovery ...
BRU was expecting to find a file header block while reading an archive, but instead found another type of block. This warning will occur if you started reading an archive at a volume other than the first, or skipped a volume in the middle of reading an archive. This error message can be suppressed with the -QV option flag. For more information on the optional flag see Chapter 8. BRU will scan each successive archive block looking for a file header block, and normal processing will resume from the first file header block found.

[W012] filename: no file: errno = code, description
The named file does not exist or part of the path name of the named file is not searchable given the current permission settings.

[E013] filename: can’t stat: errno = code, description
The UNIX stat system call failed. This means that BRU was unable to obtain status information (ownership, access and modification times, link count, etc.) on the file. The reason for the error is indicated by the UNIX error message. Generally, this error is caused because the file is not accessible with the user’s current permission settings. On networked systems, it may occur when trying to access remote (NFS-mounted) files. If this is the case, you should check your network permission settings.

[E014] pathname path too big (1023 max)
This error was caused when BRU detected a pathname longer than 1023 characters. No known UNIX system allows pathnames longer than 1023 characters, so this message may indicate that the filesystem is potentially corrupted or that something else is seriously wrong.

[E015] *** OBSOLETE MESSAGE NUMBER ***

[E016] filename: can’t open: errno = code, description
BRU could not open filename. The reason is given as part of the UNIX error message. In many cases, this is caused by insufficient file access permissions.

[W017] filename: warning - file close error: errno = code, description
BRU received an error when attempting to close the file filename. The reason for the error is given by the UNIX error message.

[E018] filename: read error: errno = code, description
BRU received an error while reading a file. The reason is indicated by the UNIX error message. This message means that the file was not backed up properly. It may be an indication of hard disk failure, a corrupted filesystem, a damaged file that is unreadable, or other system problems (like an NFS problem.)

[W019] filename: warning - file was truncated
The file filename was truncated while BRU was in the process of reading or writing it. Usually, another program has modified the file that BRU was reading. This can occur if you are attempting to back up database files and the database program is active. If BRU was creating an archive at the time, the archived file is padded with sufficient null characters to bring it back to the size it was originally (the size of the specified file when BRU began to archive it). This is the same size recorded in the file header block. If this message occurs while backing up, the data archived from filename is probably not correct (because the data was changed while BRU was reading it). Even though BRU may restore this file later without any warnings, the data could contain errors. If this message occurs while restoring an archive, it indicates that a problem occurred and that BRU was unable to restore data from the last part of the file.

[W020] filename: warning - file grew while archiving
The file filename grew in length while BRU was in the process of reading it. If BRU was creating an archive at the time, the archived file was truncated to it’s original size (the size of the file when BRU started to read it). This is the size recorded in the file header block. This warning is commonly seen for log or database files, to which information is constantly being added. It can generally be avoided by backing up the system in single user mode (or by shutting down the database before doing a backup). If the file causing this message is not critical (i.e. log files like /var/log/bruexeclog) you may wish to exclude these files from the backup. This can be done by specifying a pattern in the bruxpat file and using the -QX option.

[W021] filename: warning - can’t set user id: Not owner
BRU attempted to extract filename which was stored with the suid bit set and the user running BRU was not the original owner of the file (and did not have superuser privileges).

[W022] filename: warning - can’t set group id: Permission denied
BRU attempted to extract filename which was stored with the sgid bit set and the user running BRU was not the original owner of the file (and did not have superuser privileges).

[E023] filename: can’t exec: errno = code, description
BRU could not execute the file filename for the reason given as part of the UNIX error message. Generally, this error occurs because filename does not exist, or it was not executable by the user running BRU.

[E024] can’t fork, try again: errno = code, description
This error was caused when BRU couldn’t execute a fork system call. The reason is indicated by the UNIX error message. Generally, this indicates the system is in serious trouble, or the per-user limit on processes has been exceeded.

[E025] unrecognized wait return statcode
The wait system call returned a status code of statcode which BRU was not able to understand. If this error occurs it may indicate that there is a problem with your system or that your version of BRU is incompatible with your current version of UNIX. If you have upgraded your operating system, you may also need to upgrade your copy of BRU.

[E026] child interrupted: errno = code, description
The child process which BRU was waiting for was interrupted. The reason for the error is indicated by the UNIX error message.

[E027] filename: fatal error; stopped by signal sigcode
The child process, filename, which BRU was waiting for was stopped by a UNIX signal. The reason is indicated by sigcode.

[E028] filename: fatal error; terminated by signal sigcode
The child process, filename, which BRU was waiting for was terminated by a UNIX signal. The reason is indicated by sigcode.

[W029] filename core dumped
BRU was waiting for a child process, filename, which terminated abnormally and dumped to core.

[E030] inconsistent wait status wait code
BRU received an unexpected return code of wait code from a UNIX wait system call. Usually, the child process which was being run has gone berserk in some manner. This error may indicate that there is a problem with your system or that your version of BRU is incompatible with your current version of UNIX. If you have upgraded your operating system, you may also need to upgrade your copy of BRU.

[E031] can’t set uid to userid: errno = code, description
BRU received an error when trying to run the setuid system call. The reason is given by the UNIX error message. If this error occurs, it indicates a possible UNIX system bug or an internal bug in BRU.

[E032] can’t set gid to groupid: errno = code, description
BRU received an error when trying to run the setgid system call. The reason is given by the UNIX error message. If this error occurs, it indicates a possible UNIX system bug or an internal bug in BRU.

[W033] filename: warning - error count block checksum errors
While reading an archive, BRU detected errcount number of checksum errors in the specified file. This message can occur if the archive was originally written with errors-possibly caused by a buffer size setting that is too large. Try setting the buffer size to a smaller value when creating the archive (i.e. set bufsize=10K in the brutab file or use the -b 10K option on the command line). When reading an archive, BRU normally attempts to read the archive with the write buffer size (it obtains the write buffer size from the archive header block stored at the start of the archive). The proper buffer size varies with the system and type of tape drive. In some cases, a tape written on one system (with a large buffer size like 64K) cannot be read properly on another system (which can only handle a small buffer size like 10K). If this is the case, you may be able to force BRU to read the tape by forcing the buffer size to smaller value (i.e. specify -b 10K as one of the command line options). Checksum errors may also be caused by hardware or tape problems. Try cleaning the heads on your tape drive. Try to retention the tape. Also, make sure that your tape cartridges are in good shape-tapes do not last forever. They should be rotated frequently and replaced on a regular basis. Make sure that you are using the proper kind of tape with your tape drive. Many tape cartridges look the same (especially 1/4” tapes), but have different densities. For instance, if you have a 150 MB tape drive, you should use 150 MB (DC6150) or 250 MB (DC6250) tape cartridges. You will get errors if you try to write to a 60 MB (DC600A) tape.

[E034] internal bug in routine routinename
BRU detected some sort of internal bug in the routine routinename. If this error occurs, it may possibly be a bug in BRU, or a hardware or kernel software problem. If it is not repeatable, it is likely to be a hardware or kernel bug. This message should be reported to TOLIS Group Tech Support.

[E035] can’t allocate byte_count more bytes: errno = code, description
BRU ran out of memory for some reason. This error generally occurs when BRU tries to create a tree from a list of filenames read from the standard input, or when memory is very limited on the system due to hardware or CPU constraints.  

[E036] internal error in tree; pathname overflow
While building a file tree, BRU created a path which exceeded 1023 characters in length. No known UNIX system allows pathnames longer than 1023 characters, so this message may indicate that the filesystem is corrupted or that something else is seriously wrong.

[E037] *** OBSOLETE MESSAGE NUMBER ***

[E038] filename: seek error: errno = code, description
BRU received an error when attempting to seek to a certain location in the file that it was reading or writing. The name of the file is indicated by filename. The reason for the error is given by the UNIX error message. This error is rare and usually indicates a hardware problem with the disk drive.

[W039] warning - info block checksum error
BRU detected a checksum error while reading the first block of an archive. The info block (archive header block) contains information about the archive which is of use to BRU, but not critical to reading or extracting files from the archive. Make sure that the archive you are attempting to read was actually written by BRU. This error often occurs when attempting to read a tape written by another program (like tar or cpio). It may also occur if you try to read a tape that is blank. If this is the ONLY warning or error message (and BRU appeared to work normally), it can usually be ignored. In this particular case, it means that BRU had trouble reading the first block of the archive, but was able to skip past the first block and read the rest of the archive normally.  

[E040] filename: write error: errno = code, description
BRU received an error when attempting to write to the file filename. The reason for the error is shown by the UNIX error message. If this error occurs, it usually indicates a hardware problem with your hard disk. It could also indicate that the filesystem containing filename is out of space, or that the filesystem is write- protected (it may be mounted as “read-only” or you may not have write permission).

[W041] filename: warning - error setting mode: errno = code, description
BRU received an error when attempting to set the mode of filename. The error occurred when BRU was executing the system call chmod. The reason is indicated by the UNIX error message.

[W042] filename: warning - error setting owner/group: errno = code, description
BRU received an error from the operating system when attempting to set the owner id or group id of filename. The error occurred when BRU was executing the system call chown. The reason is indicated by the UNIX error message. On systems which support symbolic links, this error can occur when BRU attempts to set the owner/group id of a symbolic link which points to a file which does not exist. This can occur if the symbolic link filename is restored, but the file the symbolic link points to is not restored.

[W043] filename: warning - error setting times: errno = code, description
BRU received an error from the operating system when attempting to set the access and modification times of filename. The error occurred when BRU was executing the system call utime . The reason is indicated by the UNIX error message.

[E044] filename: error making node: errno = code, description
BRU received an error when attempting to create a special file system node, such as a FIFO, block special file, or character special file. The error occurred when BRU was executing the system call mknod. The reason is indicated by the UNIX error message. This message may occur when trying to restore special files and you do not have superuser privileges. On some systems, only the root user has the ability to create special files.

[E045] filename1: can’t link to filename2: errno = code, description
BRU received an error when attempting to make a hard link between filename1 and filename2. The reason is indicated by the UNIX error message. This message occurs when filename2 already exists and cannot be overwritten by a link.  

[E046] internal error; inconsistent phys blk addrs

[W047] warning - missing archive header block; starting at volume volnum
BRU couldn’t find an archive header block at volume number volnum. This warning is normal when BRU is asked to start reading an archive at some other volume than the first volume. For example, you will see this message if you immediately try to restore files from the 3rd tape of an archive (without reading through the 1st and 2nd tapes). If you want to start from a different tape other then the first tape. You must use the -QV option, this will suppress the error message.

[W048] filename: warning - lost linkage: errno = code, description
BRU could not preserve the linkage of two files. The reason is indicated by the UNIX error message. Generally, this error is seen when BRU ran out of memory when it attempted to allocate memory internally to maintain the linkage information of the specified file. In this case, the file would be archived as two separate, distinct files in the archive. Only the linkage information would be lost.

[W049] filename: warning - linknum unresolved link(s)
While archiving the file filename, BRU detected linknum number of unresolved links to filename. This error is generated when there is still another pathname which points to filename which does not appear in the archive. Usually, this message occurs when BRU is asked to archive a set of directories that contain files that have hard links to files located in other directories (that are not archived by BRU). This message can be disabled by specifying the -l option on the command line.

[W050] ttyname: warning - can’t open for interaction: errno = code, description
BRU could not open the tty stream ttyname to interact with the user. The reason for the error is given by UNIX error message. This message may occur when attempting to run BRU in the background and the -B option (background mode) has not been specified. When run in the foreground, BRU attempts to use the /dev/tty device to communicate with the user. In background mode, /dev/tty is not available. In this case, the interaction pathnames can be specified with the -Iq,queryfile and -Ir,replyfile options on the BRU command line (this is normally used when running BRU with the brutalk program).

[E051] date conversion error: date
The string specified by date is not in the proper format or is not a legal date and time.

[W052] warning - uname failed: errno = code, description
BRU received an error when attempting to execute the uname system call. The reason is indicated by the UNIX error message.

[W053] warning - label string too big
BRU has a string length limit of 63 characters for a user specified label (used with the -L option). You must shorten the length of your label string.

[E054] error - invalid uid/filename as -o argument: pattern
BRU could not convert a given symbolic user name to the internal numeric form. This error usually occurs when the -o option is used and BRU cannot find username in the /etc/passwd file.

[E055] error - illegal wildcard pattern: pattern, errmsg
The wildcard matching pattern specified by pattern is not legal. The reason is indicated by errmsg.

[E056] filename: can’t overwrite: errno = code, description
The file filename could not be overwritten during extraction. The reason is indicated by the UNIX error message. In most cases, this message is due to a permissions problem.

[W057] filename: can’t access for write: errno = code, description
The file filename could not be accessed for write. The reason is indicated by the UNIX error message. In most cases, this message is due to a permissions problem.

[W058] filename: can’t access for read: errno = code, description
The file filename could not be accessed for read. The reason is indicated by the UNIX error message. In most cases, this message is due to a permissions problem.

[W059] filename: warning - will not be contiguous: errno = code, description
BRU was unable to create the file filename as a contiguous file. The reason is indicated by the UNIX error message. This message should only occur on systems that support contiguous files (like Masscomp or HP-UX).

[W060] filename: warning - contiguous files not supported, extracted as a regular file
The file filename cannot be restored as a contiguous file, so BRU will create a regular UNIX file instead.

[E061] can’t read both file list and archive from stdin!
BRU was instructed to read both an archive and a list of files from the standard input stream. This error occurs when an illegal BRU command like the following is entered: bru -x -f - -

[W062] warning - premature end of volume volnum
When reading/writing an archive device, BRU encountered an end-of-file (or got an I/O error) before reaching the expected end of the archive. This message is often preceded by messages [W004] or [W005]. In this case, it may indicate a problem with the tape drive hardware, old or damaged tapes, or incompatible tape formats (i.e. trying to write to a 60MB tape cartridge on a 150MB tape drive).

[W063] warning - media appears to be unformatted: errno = code, description
When BRU first attempted to read/write to a device it received an error. The reason is indicated by the UNIX error message. If BRU receives an error on the first read or write to an archive device, and the error conditions match the values set in the brutab entry for unformatted media in this device, BRU will issue this warning message. When writing, if the format and fmtcmd= parameters are set for the device, this warning will be suppressed and BRU will attempt to format the media.

[O064] *** OBSOLETE MESSAGE NUMBER ***

[W065] warning - using internal default device table
BRU could not find the brutab file specified by the BRUTAB environment variable, or the default brutab file located in /etc/brutab. In this case, BRU used its internal brutab, which may not be correct for the current archive device.

[I066] filename: not restored
This is an informational message. BRU did not restore the file filename because the current file (on the disk) has a modification time that is newer than the file read from the archive. This is BRU’s default method of restoring files. If you wish to overwrite all files, regardless of date, you should add the -ua option to the BRU command line.

[W067] warning - media appears to be write protected or wrong density
BRU received an error on its first attempt to write to an archive device. BRU has determined that it might be caused by media that is write-protected. The UNIX system may not return the proper error code, so it is not always possible for BRU to determine if the media is actually write-protected. BRU tries to determine the write-protect status by comparing the errno code returned by UNIX with the value of wperr (as specified for the device in the brutab file). If wperr=0 (or is not set) then BRU must “guess” at whether the device is truly write-protected. In this case, it assumes that an error on the first write attempt is caused by write-protection, and issues the above message.

[W068] filename: warning - not found or not selected
The user specified a file on the command line which BRU did not find. The file filename may not exist or may be spelled incorrectly. If you are attempting to extract (restore) a file, make sure that filename EXACTLY MATCHES with the desired filename on the archive, including any beginning slashes. For example:
  /myfile DOES NOT MATCH./myfile.

[W069] warning - may have to use -F option to read archive
BRU encountered an archive which does not appear to have checksum. The archive may have been written with -F option (which is not recommended) and must be read with the same option. This message sometimes occurs when BRU attempts to read an archive that was written by another program, like tar or cpio. It can also occur when BRU has trouble reading a BRU archive due to bad tapes, dirty tape heads, hardware problems, incompatible tape formats, etc.

[E070] interaction needed, aborted by -B option
BRU was run with the -B option, indicating that it is running in background mode and that no user interaction is possible. It encountered a condition that required user interaction (like loading a new tape) and terminated. The -B option is normally set automatically when BRU is started in the background, so this message may occur even if -B was not explicitly specified.

[E071] filename: error making directory: errno = code, description
BRU received an error when attempting to create a directory. The reason is indicated by the UNIX error message. In most cases, this occurs when the user has insufficient permissions.

[E072] filename: error reading symbolic link: errno = code, description
BRU could not read a symbolic link for some reason. The reason is indicated by the UNIX error message.

[E073] filename: symbolic links not supported
While running on a system that does not support symbolic links, BRU encountered a symbolic link while comparing an archive in differences mode (-d option).

[E074] filename: could not make symbolic link: errno = code, description
While extracting the symbolic link filename, BRU was unable to create a symbolic link. The reason is indicated by the UNIX error message. This error will occur if your version of UNIX does not support symbolic links.

[E075] filename: could not make fifo
BRU tried to extract a FIFO (named pipe file) on a system which does not support FIFOs. Normally, BRU tries to create a regular file with the same name. In this case, the attempt to create a regular file was unsuccessful.

[W076] warning - link of filename to dirname, dirname is a directory, no link made
BRU was asked to create a symbolic link from filename to the directory dirname, on a system which does not support symbolic links. Since hard links to directories are not allowed by UNIX, this warning is issued and no link is made.

[W077] warning - link of filename1 to filename2, filename2 does not exist
BRU attempted to create a hard link from filename1 to filename2 and filename2 does not exist. Generally, this message occurs when BRU is asked to do a partial restore and filename2 is not present.

[W078] warning - extracted fifo filename as a regular file
BRU was asked to extract a FIFO named filename on a system which does not support FIFOs. It extracted filename as a regular file. The correctness or desirability of this behavior is subject to debate, which is why the warning is issued.

[W079] filename: warning - linkcount additional link(s) added while archiving
While BRU was archiving a file, there were linkcount additional links made to it. These additional links may or may not have been archived.

[W080] *** OBSOLETE MESSAGE NUMBER ***

[E081] no default device in brutab file, use -f option
BRU could not find a default device in the brutab file. The default device is always the first device entry in the brutab file.

[EO82] *** OBSOLETE MESSAGE NUMBER ***

[W083] warning - attempt to change buffer size from oldbufsize to newbufsize ignored (incompatible brutab entries)
BRU detected different default buffer sizes when reading or writing to multiple devices (device cycling). The buffer size is not allowed to change between volumes of an archive. This error usually occurs at the start of the second device, when BRU reads the bufsize parameter for that device (from the brutab file) and discovers that the buffer size differs from the size used by the first device. To avoid this warning message, use the -b option to force a specific buffer size for all devices.

[E084] double buffering I/O error, bytecount bytes read/written: errno = code, description

[E085] problem setting up double buffering, using normal buffering
Both of these errors indicate that BRU encountered a problem setting up the double buffering. Sometimes, reducing the I/O buffer size will remedy the problem.

[E086] filename: media ejection failed: errno = code, description
On systems which support ejection of archive media under software control, BRU may be configured to eject each media when it is done with the media. BRU encountered some sort of error while attempting to eject the media.

[I087] filename: compressed version was larger, stored uncompressed
When file compression is utilized via the -Z option, BRU will check to ensure that the compressed version of the file uses fewer archive blocks than the uncompressed version. If the compressed version will not result in any savings in archive space (it is larger than the normal file), then the uncompressed version will be archived instead.

[E088] filename: decompression failed (errmsg)
BRU received an error from when attempting to decompress a file. The reason is indicated by errmsg. The file filename has not been extracted properly and may contain errors.

[W089] warning - estimate mode ignores compression
BRU was told to use both the -e and -Z options simultaneously. Because of the large overhead in compressing files, and because there is no way to determine the compression ratio without actually doing the compression, BRU cannot estimate how much archive space is required for an archive when compression is enabled. Therefore, the -e option ignores possible savings due to compression.

[W090] filename: warning - not deleted: errno = code, description
BRU received some sort of error while attempting to delete (unlink) filename.

[W091] filename: warning - compression failed, stored uncompressed
BRU received an error from UNIX when BRU attempted to compress filename for storage (such as a filesystem temporary space overflow). BRU could not generate the compressed version of the file. Thus, the file was stored uncompressed.

[E092] *** OBSOLETE MESSAGE NUMBER ***

[W093] warning - buffer size bufsize exceeds system imposed limit buflimit with double buffering
While attempting to set up double buffering using System V Style shared memory support, BRU was asked to use an I/O buffer size which resulted in the double buffering buffers exceeding the system imposed shared memory limits. Try setting shmmax to a smaller value.

[W094] warning - buffer size automatically adjusted to bufsize
While attempting to set up double buffering using System V Style shared memory support, BRU was asked to use an I/O buffer size which resulted in the double buffering buffers exceeding the system imposed shared memory limits. The I/O buffer size was automatically adjusted downwards to the maximum size which the system could support.

[E095] could not get shared memory segment: kilobytes: errno = code, description
BRU was attempted a system call to shmget and was unable to get the requested amount of shared memory. The reason is indicated by the UNIX error message.

[E096] could not attach shared memory segment: errno = code, description
BRU made a system call to shmget which failed after BRU had already made a successful shmget call. The reason for the error is indicated by UNIX error message.

[E097] could not allocate message queue: errno = code, description
BRU could not allocate the memory needed to perform double buffering (-D option). The reason is indicated by the UNIX error message. Your system may not support shared memory, or the shared memory parameters (shmmax, shmseg, shmall) may not be set correctly in the brutab file.

[E098] warning - don’t understand -I option badargs
The string badargs was not recognized as a valid argument for the interaction option -I.

[W099] warning - need more than segments shared memory segments
BRU was not able to allocate enough shared memory segments. Try setting the shmseg parameter for the device in use to a lower value.

[W100] warning - failed to move break value by {number of bytes} bytes: errno = code, description
BRU made a system call to sbrk which failed. BRU was unable to adjust the break value. This message is only caused when BRU was previously able to adjust the break value to the desired place; or should be able to adjust the break value, such as when reducing the amount of memory used.

[W101] warning - compression initialization failed, -Z suppressed
BRU could not acquire sufficient memory to perform the requested file compression. Compression was not performed. Try reducing the number of bits in compression by using the -N option with a lower value.

[W102] warning - unknown child died, pid pidnumX(expected pidnum), status statcode
While waiting for a specific child process to exit, the wait system call returned to BRU the pid of another process, pidnumX, which exited with the status of statcode. This error should never occur. If this error occurs, it is usually indicative of a serious problem with the system.

[E103] double buffer child died, status statcode
The child process used by BRU for double buffering died unexpectedly. The reason is indicated by the UNIX status code statcode.

[E104] warning - double buffer child error errcode
The child process used by BRU for double buffering received some sort of fatal error, which the child process was able to recognize as unrecoverable. The reason for the error is indicated by errcode.

[W105] warning - no double buffer child to reap: errno = code, description
BRU was waiting for a double buffer child to exit and the wait system call failed for some reason which was unexpected in the parent process.

[W106] warning - archive device may need “shmcopy” flag set in brutab entry
On some systems, the device driver for a given archive device may not be able to do I/O directly to or from shared memory. BRU detects this condition when the first write to, or the first read from, a given device fails with UNIX error code errno set to EFAULT. BRU issues this warning message and automatically attempts to switch to a mode where the data is copied to or from a local buffer. This automatic switching generally succeeds on writes and fails on reads, which is why the suggested fix is printed as a warning message.

[E107] filename: error - unrecoverable archive write error, some data lost: errno = code, description
BRU received an unrecoverable write error while creating an archive, and all or part of the data was lost for filename. This message may be an indication of tape hardware problems, dirty tape heads, an improper BRU buffer size, tapes that need retensioning, or tapes that are simply worn out. On high-density tape drives, this message can occur when an attempt is made to write to a low-density tape. Usually this happens with 1/4” tape cartridges, which all look similar. For example, this error will occur when using a 150MB tape drive to write to a DC600A (60MB) or DC300 (30MB) tape cartridge. High-density tape drives can normally read low-density cartridges, but they cannot write to them.

[W108] warning - media appears to be unformatted or write protected: errno = code, description
This is a general warning which may appear on the first attempt to read or write an archive volume which is unformatted, or when an attempt is made by BRU to write to an archive which is write- protected. The reason for the warning is indicated by the UNIX error message. This warning may also occur if the backup device does not respond properly when BRU attempts to open the device for writing. BRU is “faked out” and thinks that the device is write-protected. This often occurs with on the first attempt to write to a SCSI device. Try repeating the command. If BRU works successfully, this message can be safely ignored.

[W109] warning - assuming end of volume volnum (unknown size)
BRU encountered an unrecoverable read or write error before reaching the end of an archive while reading or writing a volume of unknown size. BRU may have actually reached the end of the volume, or BRU may have simply reached a bad spot on the media, which BRU cannot proceed past. Because BRU does not know the media size, BRU has no way of knowing the difference, hence, the warning message. If no other warnings, or errors, occur, this warning is benign.

[W110] warning - found volume volnumX, expecting volnum
BRU was expecting to find volume volnum and it encountered a different volume. Remove the volume and replace it with the correct volume.

[O111] *** OBSOLETE MESSAGE NUMBER ***

[W112] warning - volume not part of archive created archivedate
BRU received the correct volume number, but the date of the volume differs from the current archive. Generally, this warning occurs when the wrong tape is inserted while attempting to extract an archive.

[A113] alert - all data currently on devicename will be destroyed
When the brutab entry for a device includes the qfwrite boolean value, this message will be issued on the first write to the first volume placed in that device, and BRU will wait for confirmation to continue. In devices which might share both mounted and unmounted media, this prevents inadvertently overwriting media which may have been left in the device by mistake.

[I114] *** OBSOLETE MESSAGE NUMBER ***

[A115] *** OBSOLETE MESSAGE NUMBER ***

[I116] *** OBSOLETE MESSAGE NUMBER ***

[I117] don’t know how to rewind archive device
BRU doesn’t know how to rewind the present archive device.

[A118] rerun with “-b bufsizek” argument
Re-run your BRU command with the specified buffer size

[Q119] action filename: please confirm [y/n/g]
BRU is waiting for confirmation of the given action. The -w flag was specified on the command line.

[Q120] query options [default: Option] >>
General message used to prompt user with various messages.

[A121] load volume volnum - press ENTER to continue on device device name

[W122] filename: warning - too large under current ulimit, not extracted
The size of filename exceeds the current ulimit. Set ulimit to a larger value and try again.

[E123] ulimit call failed to set maximum file size limit to blkcount blocks
BRU was unable to set the ulimit to a larger value.

[W124] warning - no double buffering support included in this version
Your version of BRU does not support double buffering.  BRU reverts to normally buffered I/O

[W125] warning - shared memory does not appear to be working in your kernel
Verify the settings in you kernel. Contact your UNIX provider for help.

[E126] problem sending message to other process
While in double-buffer mode, BRU could not communicate with the child process.

[E127] problem receiving message from other process: errno = code, description
While in double-buffer mode, BRU could not communicate with the child process.

[W128] filename: warning - file contents changed while archiving
BRU found that the file it was backing up had been changed. This can happen during live system backups. BRU does not lock files when reading. If a file is  modified while BRU is reading it, this message will occur.

[W129] *** OBSOLETE MESSSAGE NUMBER ***

[W130] warning - I/O error on first block
BRU cannot read or write the first block of the archive. Verify that the given device has a tape in the drive and that the tape has not been ejected.

[W131] warning - archive device may need “ignoreclose” flag set in brutab entry
We have found that some tape drives require this setting in the brutab file. For additional information on this settings please refer to chapter 4 of this User’s Guide

[W132] warning - media size automatically adjusted to size
This message is issued when BRU starts writing to a new volume and has changed the media size to a value which is different than the size originally specified. This can occur if BRU encountered the end-of-tape sooner than expected. For example, the media size was specified as 150M, but BRU hit the end-of-tape (on the first tape) at 120 Mb. BRU will then ask for the next volume and adjust the media size (for the second tape) to a value slightly less than 120 Mb.

[W133] warning - no entry for device devicename in brutabfile
BRU could not locate an entry in your brutab file for the given device.

[E134] internal error errcode - failed self consistency and portability checks
This indicates that the BRU executable file has been damaged or the BRU version is not the correct one for your system. This usually occurs when BRU cannot successfully determine your timezone offset from GMT or receives a bad value for the current date and time from a tzset function call.

[E135] path beginning with filename too large (maxlen characters max)
The specified filename exceeds the system limit.  

[W136] filename1: warning - link to filename2 broken, saved as duplicate
The character length of the link name filename2, was too large to store in the file header block.

[W137] warning - wait failed: errno = code, description
During double-buffering, an error occurred while waiting for a child process.

[W083] warning - attempt to change buffer size from oldbufsize to newbufsize ignored (incompatible brutab entries)
BRU detected different default buffer sizes when reading or writing to multiple devices (device cycling). The buffer size is not allowed to change between volumes of an archive. This error usually occurs at the start of the second device, when BRU reads the bufsize parameter for that device (from the brutab file) and discovers that the buffer size differs from the size used by the first device. To avoid this warning message, use the -b option to force a specific buffer size for all devices.

[E084] double buffering I/O error, bytecount bytes read/written: errno = code, description

[E085] problem setting up double buffering, using normal buffering
Both of these errors indicate that BRU encountered a problem setting up the double buffering. Sometimes, reducing the I/O buffer size will remedy the problem.

[E086] filename: media ejection failed: errno = code, description
On systems which support ejection of archive media under software control, BRU may be configured to eject each media when it is done with the media. BRU encountered some sort of error while attempting to eject the media.

[I087] filename: compressed version was larger, stored uncompressed
When file compression is utilized via the -Z option, BRU will check to ensure that the compressed version of the file uses fewer archive blocks than the uncompressed version. If the compressed version will not result in any savings in archive space (it is larger than the normal file), then the uncompressed version will be archived instead.

[E088] filename: decompression failed (errmsg)
BRU received an error from when attempting to decompress a file. The reason is indicated by errmsg. The file filename has not been extracted properly and may contain errors.

[W089] warning - estimate mode ignores compression
BRU was told to use both the -e and -Z options simultaneously. Because of the large overhead in compressing files, and because there is no way to determine the compression ratio without actually doing the compression, BRU cannot estimate how much archive space is required for an archive when compression is enabled. Therefore, the -e option ignores possible savings due to compression.

[W090] filename: warning - not deleted: errno = code, description
BRU received some sort of error while attempting to delete (unlink) filename.

[W091] filename: warning - compression failed, stored uncompressed
BRU received an error from UNIX when BRU attempted to compress filename for storage (such as a filesystem temporary space overflow). BRU could not generate the compressed version of the file. Thus, the file was stored uncompressed.

[E092] *** OBSOLETE MESSAGE NUMBER ***

[W093] warning - buffer size bufsize exceeds system imposed limit buflimit with double buffering
While attempting to set up double buffering using System V Style shared memory support, BRU was asked to use an I/O buffer size which resulted in the double buffering buffers exceeding the system imposed shared memory limits. Try setting shmmax to a smaller value.

[W094] warning - buffer size automatically adjusted to bufsize
While attempting to set up double buffering using System V Style shared memory support, BRU was asked to use an I/O buffer size which resulted in the double buffering buffers exceeding the system imposed shared memory limits. The I/O buffer size was automatically adjusted downwards to the maximum size which the system could support.

[E095] could not get shared memory segment: kilobytes: errno = code, description
BRU was attempted a system call to shmget and was unable to get the requested amount of shared memory. The reason is indicated by the UNIX error message.

[E096] could not attach shared memory segment: errno = code, description
BRU made a system call to shmget which failed after BRU had already made a successful shmget call. The reason for the error is indicated by UNIX error message.

[E097] could not allocate message queue: errno = code, description
BRU could not allocate the memory needed to perform double buffering (-D option). The reason is indicated by the UNIX error message. Your system may not support shared memory, or the shared memory parameters (shmmax, shmseg, shmall) may not be set correctly in the brutab file.

[E098] warning - don’t understand -I option badargs
The string badargs was not recognized as a valid argument for the interaction option -I.

[W099] warning - need more than segments shared memory segments
BRU was not able to allocate enough shared memory segments. Try setting the shmseg parameter for the device in use to a lower value.

[W100] warning - failed to move break value by {number of bytes} bytes: errno = code, description
BRU made a system call to sbrk which failed. BRU was unable to adjust the break value. This message is only caused when BRU was previously able to adjust the break value to the desired place; or should be able to adjust the break value, such as when reducing the amount of memory used.

[W101] warning - compression initialization failed, -Z suppressed
BRU could not acquire sufficient memory to perform the requested file compression. Compression was not performed. Try reducing the number of bits in compression by using the -N option with a lower value.

[W102] warning - unknown child died, pid pidnumX(expected pidnum), status statcode
While waiting for a specific child process to exit, the wait system call returned to BRU the pid of another process, pidnumX, which exited with the status of statcode. This error should never occur. If this error occurs, it is usually indicative of a serious problem with the system.

[E103] double buffer child died, status statcode
The child process used by BRU for double buffering died unexpectedly. The reason is indicated by the UNIX status code statcode.

[E104] warning - double buffer child error errcode
The child process used by BRU for double buffering received some sort of fatal error, which the child process was able to recognize as unrecoverable. The reason for the error is indicated by errcode.

[W105] warning - no double buffer child to reap: errno = code, description
BRU was waiting for a double buffer child to exit and the wait system call failed for some reason which was unexpected in the parent process.

[W106] warning - archive device may need “shmcopy” flag set in brutab entry
On some systems, the device driver for a given archive device may not be able to do I/O directly to or from shared memory. BRU detects this condition when the first write to, or the first read from, a given device fails with UNIX error code errno set to EFAULT. BRU issues this warning message and automatically attempts to switch to a mode where the data is copied to or from a local buffer. This automatic switching generally succeeds on writes and fails on reads, which is why the suggested fix is printed as a warning message.

[E107] filename: error - unrecoverable archive write error, some data lost: errno = code, description
BRU received an unrecoverable write error while creating an archive, and all or part of the data was lost for filename. This message may be an indication of tape hardware problems, dirty tape heads, an improper BRU buffer size, tapes that need retensioning, or tapes that are simply worn out. On high-density tape drives, this message can occur when an attempt is made to write to a low-density tape. Usually this happens with 1/4” tape cartridges, which all look similar. For example, this error will occur when using a 150MB tape drive to write to a DC600A (60MB) or DC300 (30MB) tape cartridge. High-density tape drives can normally read low-density cartridges, but they cannot write to them.

[W108] warning - media appears to be unformatted or write protected: errno = code, description
This is a general warning which may appear on the first attempt to read or write an archive volume which is unformatted, or when an attempt is made by BRU to write to an archive which is write- protected. The reason for the warning is indicated by the UNIX error message. This warning may also occur if the backup device does not respond properly when BRU attempts to open the device for writing. BRU is “faked out” and thinks that the device is write-protected. This often occurs with on the first attempt to write to a SCSI device. Try repeating the command. If BRU works successfully, this message can be safely ignored.

[W109] warning - assuming end of volume volnum (unknown size)
BRU encountered an unrecoverable read or write error before reaching the end of an archive while reading or writing a volume of unknown size. BRU may have actually reached the end of the volume, or BRU may have simply reached a bad spot on the media, which BRU cannot proceed past. Because BRU does not know the media size, BRU has no way of knowing the difference, hence, the warning message. If no other warnings, or errors, occur, this warning is benign.

[W110] warning - found volume volnumX, expecting volnum
BRU was expecting to find volume volnum and it encountered a different volume. Remove the volume and replace it with the correct volume.

[O111] *** OBSOLETE MESSAGE NUMBER ***

[W112] warning - volume not part of archive created archivedate
BRU received the correct volume number, but the date of the volume differs from the current archive. Generally, this warning occurs when the wrong tape is inserted while attempting to extract an archive.

[A113] alert - all data currently on devicename will be destroyed
When the brutab entry for a device includes the qfwrite boolean value, this message will be issued on the first write to the first volume placed in that device, and BRU will wait for confirmation to continue. In devices which might share both mounted and unmounted media, this prevents inadvertently overwriting media which may have been left in the device by mistake.

[I114] *** OBSOLETE MESSAGE NUMBER ***

[A115] *** OBSOLETE MESSAGE NUMBER ***

[I116] *** OBSOLETE MESSAGE NUMBER ***

[I117] don’t know how to rewind archive device
BRU doesn’t know how to rewind the present archive device.

[A118] rerun with “-b bufsizek” argument
Re-run your BRU command with the specified buffer size

[Q119] action filename: please confirm [y/n/g]
BRU is waiting for confirmation of the given action. The -w flag was specified on the command line.

[Q120] query options [default: Option] >>
General message used to prompt user with various messages.

[A121] load volume volnum - press ENTER to continue on device device name

[W122] filename: warning - too large under current ulimit, not extracted
The size of filename exceeds the current ulimit. Set ulimit to a larger value and try again.

[E123] ulimit call failed to set maximum file size limit to blkcount blocks
BRU was unable to set the ulimit to a larger value.

[W124] warning - no double buffering support included in this version
Your version of BRU does not support double buffering.  BRU reverts to normally buffered I/O.

[W125] warning - shared memory does not appear to be working in your kernel
Verify the settings in you kernel. Contact your UNIX provider for help. 

[E126] problem sending message to other process
While in double-buffer mode, BRU could not communicate with the child process.

[E127] problem receiving message from other process: errno = code, description
While in double-buffer mode, BRU could not communicate with the child process.

[W128] filename: warning - file contents changed while archiving
BRU found that the file it was backing up had been changed. This can happen during live system backups. BRU does not lock files when reading. If a file is  modified while BRU is reading it, this message will occur.

[W129] *** OBSOLETE MESSSAGE NUMBER ***

[W130] warning - I/O error on first block
BRU cannot read or write the first block of the archive. Verify that the given device has a tape in the drive and that the tape has not been ejected.

[W131] warning - archive device may need “ignoreclose” flag set in brutab entry
We have found that some tape drives require this setting in the brutab file. For additional information on this settings please refer to chapter 4 of this User’s Guide

[W132] warning - media size automatically adjusted to size
This message is issued when BRU starts writing to a new volume and has changed the media size to a value which is different than the size originally specified. This can occur if BRU encountered the end-of-tape sooner than expected. For example, the media size was specified as 150M, but BRU hit the end-of-tape (on the first tape) at 120 Mb. BRU will then ask for the next volume and adjust the media size (for the second tape) to a value slightly less than 120 Mb.

[W133] warning - no entry for device devicename in brutabfile
BRU could not locate an entry in your brutab file for the given device.

[E134] internal error errcode - failed self consistency and portability checks
This indicates that the BRU executable file has been damaged or the BRU version is not the correct one for your system. This usually occurs when BRU cannot successfully determine your timezone offset from GMT or receives a bad value for the current date and time from a tzset function call.

[E135] path beginning with filename too large (maxlen characters max)
The specified filename exceeds the system limit.  

[W136] filename1: warning - link to filename2 broken, saved as duplicate
The character length of the link name filename2, was too large to store in the file header block.

[W137] warning - wait failed: errno = code, description
During double-buffering, an error occurred while waiting for a child process.

[E138] error - unable to format device devicename
BRU could not format the device. It may be write protected, or command specified by fmtcmd= failed when attempting to format the device.

[E139] error - timed out during execution of pid pidnum
BRU attempted to execute an external program and the process timed out.

[W140] error - unable to read include/exclude pattern file: filename
The specified include/exclude pattern contains an error. BRU could not read the file.  

[W141] warning - bruxpat pattern: pattern, errmsg
The specified include/exclude pattern contains an error. The reason for the error is indicated by errmsg. Edit the bruxpat file to correct the problem.

[W142] -E option ignored with -c, -e, -i or -t options
This is an illegal command option for the given modes ( -c -e -i or -t)

[I143] rewinding volume [volnum] to begin autoscan
BRU prints this informational message to let you know it is rewinding volume number volnum to begin the AUTOSCAN. Rewinding may sometimes take a substantial (several minutes) length of time, it depends on the speed of your tape drive.

[I144] begin autoscan of volume [volnum]
BRU prints this informational message to let you know it has begun the auto-scanning of volume number volnum. Auto-scanning may sometimes take a substantial (several minutes to over an hour) amount of time, depending on the speed of your archive device.

[E145] autoscan checksum error at block blocknum (kbsize)
BRU detected a problem while performing a checksum validation during the AUTOSCAN phase. It could be an indication of tape hardware problems, dirty tape heads, an improper BRU buffer size, tapes with the wrong density, tapes that need to be retensioned, or tapes that are simply worn out. If this message occurs at the beginning of a tape (blknum is less than 10), it may indicate that your tape drive (or device driver) contains a bug and returned control to BRU before it finished rewinding. BRU tried to start the AUTOSCAN, but was unable to read the tape (because it was still rewinding). Often this problem can be fixed by setting the maxrewindtime parameter for your device in the /etc/brutab file. A setting of maxrewindtime=300 seems to work for most tape drives. Sometimes this message occurs with tape drives that are confused by BRU’s overwrite-protect feature. If overwrite-protect is enabled, BRU attempts to read the tape before it tries to write. Some tape drives cannot handle this. If this is the case, edit the /etc/brutab file and disable the global brutab parameter “#+ OVERWRITE PROTECT” by removing the “+” sign or by deleting the line.

[E146] unable to get memory (bytecount bytes) needed for autoscan buffer
BRU is unable to allocate enough memory to create an AUTOSCAN buffer. This message usually indicates that the buffer size (the bufsize or asbufsize parameters in /etc/brutab) is too large. It may also be caused by a shortage of memory or by system problems.

[W147] cannot do autoscan - device ‘devicename’ has “flagname” flag set in brutab
This usually indicates that the norewind or noautoscan flags are set in the device entry in your /etc/brutab file.

[E148] autoscan read error at block blknum (kbsize): errno = code, description
BRU received an error when attempting to read an archive during the AUTOSCAN phase. The reason for the error is indicated by the UNIX error message. This message may be an indication of tape hardware problems, dirty tape heads, an improper BRU buffer size, tapes with the wrong density, tapes that need retensioning, or tapes that are simply worn out. Often, this message occurs along with [E145]. Refer to its description for more information.

[W149] autoscan detected errors - media or hardware may be bad
This message indicates that errors or warnings were detected during the AUTOSCAN phase.

[I150] autoscan of blkcount blocks on volume [volnum], time, speed Kb /sec

[L151] autoscan of blkcount blocks on volume [volnum], time, speed Kb/sec
These messages are completion messages for the AUTOSCAN pass.

[E152] error - timed out trying to open filename
BRU timed out while trying open a device or file.

[E153] error - timed out trying to read
BRU timed out while trying read form a device or file.

[E154] error - timed out trying to write
BRU timed out while trying to write to a device.

[E155] error - memory fault (SIGSEGV)
BRU received a SIGSEGV signal from your OS.  This is generally indicative of a memory issue in your system.

[E156] error - memory fault (SIGSEGV) in child process
BRU received a SIGSEGV signal from UNIX on one of its child processes.  This is generally indicative of a memory issue in your system.

[E157] error - received terminate signal (SIGTERM)
BRU received a SIGTERM signal from your OS.

[E158] error - received quit signal (SIGQUIT)
BRU received a SIGQUIT from your OS.

[E159] error - received interrupt signal (SIGINT)
BRU received a SIGINT signal from your OS.

[E160] error - received hangup signal (SIGHUP)
BRU received a SIGHUP signal from your OS.

[E161] error - received strange signal (signame)
BRU received an unexpected signal.
For more information on the various signals please refer to your operating systems documentation or contact the OS manufacturer.

[W162] warning - unable to open execution log file ‘logfilename’: errno = code, description
BRU was not able to open the bruexeclog file. This could be due to a permissions problem or the location of the file is not what BRU expected. With every BRU command or operation BRU will attempt to make an entry to the BRUEXECLOG file.

[L163] START (info), CMD = ‘cmdline’
The entry in you BRUEXECLOG and to your screen shows that actual command that was started during your BRU process. It also shows you the release and version of BRU you are running.

[L164] START - child process for double-buffering

[L165] FINISH - warncount warnings, errorcount errors, exit code = exitcode

[L166] starting volume volnum on device “devicename”

[L167] device = devicename, buffer = bufsizeK bytes, media size = size

[E168] *** OBSOLETE MESSSAGE NUMBER ***

[E169] error - bad argument for -T option
The user entered BRU options in an illegal combination.

[E170] error - illegal combination of mode options (-cdeghitx)
The user entered BRU options in an illegal combination.

[W171] warning - needs to be owned by root and have suid bit set

[W172] warning - cannot open device ‘devicename’ to do autoscan
BRU could not open devicename to perform AUTOSCAN verification.

[E173] error - exceeded warning count limit of maxwarn
BRU exceeded the maximum number of allowed warnings and terminated. The maximum number of warnings can be changed with the BRUMAXWARNINGS environment variable.

[E174] error - exceeded error count limit of maxerror
BRU exceeded the maximum number of allowed errors and terminated. The maximum number of errors can be changed with the BRUMAXERRORS environment variable or the BRUMAXERRORS GLOBAL BRUTAB setting - see Chapter 4.

[E175] error - bad pattern match on: {/etc/bruxpat}, entry
This would and should be superseded by [W141].

[E176] error - bad raw block size = blksize, cannot extract raw file ‘filename’
BRU cannot restore or extract the given raw file from the archive. The information specified in the BRURAW file has an incorrect block size defined.

[W177] warning - specified size is too large, try setting size to newsize Kbytes
BRU has determined that the size given for the device you are using as an archive deice is to high. BRU has suggested that you use a smaller size as the one specified in this warning message.

[L178] rewinding volume [volnum] to begin autoscan
BRU writes this message to the bruexeclog to time stamp when it began to rewind volume volnum prior to starting an AUTOSCAN. Rewinding may take a substantial (several minutes) amount of time.

[L179] issued reset cmd ‘cmdstring’
BRU has reset the device as specified by the reset command you defined in the BRUTAB file

[W180] warning - reset cmd error: errno = code, description
BRU received a UNIX error message when attempting to reset the device with the given reset command as specified in the BRUTAB file.

[I181] read/wrote blkcount blocks on volume [volnum], time, speed Kb/sec
This reports the number of blocks written/read during the current BRU process. This will also indicate the speed at which the process ran by showing you the time and speed in Kb/sec.

[L182] read/wrote blkcount blocks on volume [volnum], time, speed Kb/sec
This reports the number of blocks written/read during the current BRU process. This will also indicate the speed at which the process ran by showing you the time and speed in Kb/sec

[W183] skipped autoscan of volume [volnum]: reason
BRU prints this message to let you know it has skipped the AUTOSCAN of volume volnum. The reason is indicated as part of the message.

[I184] waiting time seconds to finish rewind
Reports that BRU is waiting a certain amount of seconds before attempting to complete the process

[L185] waiting time seconds to do rewind
Reports that BRU is waiting a certain amount of seconds before attempting to complete the process

[L186] using ‘rshname’ as remote shell
BRU will use the given file name as it’s remote shell

[E187] unable to execute remote shell ‘rshname’
BRU is unable to use the given filename as the remote shell. Verify that it exists and that you have the proper permission set.

[E188] cannot find remote shell to execute
BRU can not execute the remote shell. Verify it is in the correct location and that you have proper permissions set.

[A189] filename is not a device
You have attempted to write to a file name. BRU is reporting that this is not a device but a file.

[A190] file filename already exists
BRU is reporting that you are attempting to write to a file that already exists on the system.

[E191] error - compression buffer too large, cannot allocate kbcountk bytes
The given ZBUFSIZE in your BRUTAB file is too large for your system to support. You should change the ZBUFSIZE setting in your BRUTAB file to a smaller number then re-attempt your process.

[E192] filename: compression error (errmsg), data is corrupted
An error occurred while BRU was compressing filename, the reason for the error is indicated by errmsg. The file was not backed up properly and the archived file contains errors. Normally, this error is caused when BRU attempts to back up a file that was changing (like a database file). For information, refer to “Live System Backups” in Chapter 9. In a few rare occurrences, this error has been caused by disk controller hardware failures or by corrupted filesystems.

[E193] filename: decompression error (errmsg)
An error occurred during the restore and decompression of a compressed file. The errmsg will indicate what the problem is with the file.

[E194] filename: warning - file was not backed up: errno = code,
This message is issued when BRU encounters a problem on its first attempt to read filename. Often, this is caused by improper permissions. If filename is part of an NFS-mounted filesystem or the /etc/export file (and BRU is running as root), this message can occur if BRU is unable to access the file due to insufficient root permissions. You may need to modify your network security parameters by editing your /etc/hosts.equiv or .rhosts file. Configuring network security can get complicated (and all networks are different), so refer to your UNIX network documentation for details.

[Q195] enter new device name [default: devicename] >>
BRU is requesting that you enter a new device name or to continue the operation on the default device.

[E196] error - attempt limit exceeded ... BRU terminated
BRU has reached it’s maximum numbers of errors given in the BRUTAB file.

[E197] error - illegal device name ... BRU terminated
BRU has attempted to write to a device that is not stated in the BRUTAB file. The setting in BRUTAB of BRUTABONLY=YES has forced this error. By changing the default value to NO for this setting you will be able to write to this device.

[W198] try using a smaller buffer size (like bufsizeK)
BRU is attempting to write to a device that is responding with errors. BRU has determined this write error as having to large of a buffer size setting set for the given device. By using the -b option in your command line and change the buffer size to a smaller size BRU might be able to complete the operation.

[A199] OVERWRITE PROTECT: volume is from archive written on date
BRU has found that the date of this archive is within it’s overwrite protect setting.

[A200] insert another volume and press ENTER to continue
Query message asking for a different tape.

[E201] user entered Q => QUIT in routine routinename
A user entered Q to quit the operation on one of BRU query to the terminal .

[I202] switching to next device
This is an information message stating that BRU is switching to a different tape drive. This message is sent during a device cycling operation

[I203] device cycling discontinued
BRU has stopped device cycling.

[W204] filename filename1 too long, changed to filename2
This message occurs when BRU restores a file with a name that is longer than 14 characters (the maximum on older UNIX systems). BRU automatically renames the file and shortens it to 14 characters. If your system supports filenames longer than this, this behavior can be suppressed. Simply add the global brutab parameter “#+ MAXFILENAMELEN=255” to the beginning of the /etc/brutab file.

[I205] filename is an existing directory
The given file name in filename is a directory

[W206] regular expression error, string

[E207] error - failed MOUNTCMD/UNMOUNTCMD of volume volnum on device device name (exit code = #)
BRU attempted to run the specified MOUNT and UNMOUNT commands as was not able to complete the operation. The device and volume number is listed in the error message.

[W208] warning - autoscan buffer size adjusted to newbufsizeKb
BRU found that the given buffer size for the AUTOSCAN process had to be changed to complete the process. If you see this warning message you should adjust your BRUTAB buffer size setting to match the given size for the warning message.

[W209] warning - skipped archive file filename
BRU has skipped the file listed on the warning message.

[W210] warning - could not rewind device
BRU could not rewind the given device.

[E211] unable to write nullcount end nulls
When closing the archive for a specific write, BRU was unable to write the entire closing block of data.  This can be caused by low memory, no disk space (of writing to a disk archive), or a write failure on a tape drive.

[E212] BRU terminated, media may be write protected or wrong density
BRU could not continue to write to the device. The reason for this error could be that the configuration of the tape drive size was wrong or that you are using a different size tape on this device.

[W213] could not read password file
BRU could read your password file. This can be caused by a permissions problem. Try running the process again as root and see if that resolves the warning.

[W214] could not read group file
BRU could not read your group file. This can be caused by a permissions problem. Try running the process again as root and see if that resolves the warning.

[I215] translating filename to filename
This is a status message informing you that the filename is being translated to the new filename

[L216] translating filename to filename
This is a log entry you will not see this message echoed to the screen

[W217] warning - filename translates to “null”
BRU is reporting the given filename in your translate file is translating to null

[E218] error - unable to read translate table file: filename
BRU is reporting that it can read your translation file. Make sure that the file is in an ASCII format and is in the given directory stated in your BRUTAB file

[E219] translation table error ‘ERROR TEXT’
If you have specified a translation table via the -T command line option, BRU is unable to read the contents of the specified file.  The ‘ERROR TEXT’ will describe the exact error encountered.

[O220] *** OBSOLETE MESSAGE NUMBER ***

[E221] filename : cannot overwrite directory with file
BRU can not overwrite the directory with a file.

[E222] filename : cannot overwrite file with directory
BRU can not overwrite the file with a directory.

[E223] unable to inspect “norewind” device
The given device has the “norewind” option set in BRUTAB. With this option set BRU can not rewind the device and perform the AUTOSCAN option.

[E224] error - invalid -u argument “%s”
Invalid argument with the -u option. Valid options are ( a b c d i p r f )

[E225] error - unable to execute MOUNTCMD=”filename”
BRU can not run the given MOUNTCMD or it is attempting to run a command that is illegal.

[W226] “device” : device open when UNMOUNTCMD was called (loc=%d)
The device was open with a different request when BRU called the UNMOUNTCMD

[W227] “filename”: warning - error setting owner/group on symbolic link: errno = number,
BRU could not set the owner/group information for the specified file. The UNIX error number and description, descried the problem.

[E228] error - unable to read raw-partition file: “filename”
BRU could not read the given BRURAW file. Make sure that the file has the correct permissions and is in the given directory.

[E229] error - no raw-device description in bruraw table: “filename”
There was no information provided in the BRURAW file.

[W230] warning - invalid raw-device specified (& ignored): “filename”
A invalid device was specified in the BRURAW file BRU has now ignored that device and is not backing up the given device.

[W231] warning - problem reading label file: “filename”
BRU could not read the given file to create a label from. Make sure that the file exist and that

[W232] filename: warning - file may be locked
BRU is reporting that the given file name might be a locked file. BRU can not read the file and this might cause BRU to terminate if you have set a low setting for the maximum number of warnings.

[W233] warning - unable to read smart-restore pattern file: filename
BRU is not able to read your given SmartRestore ™ file. Verify that the file is in the correct ASCII format and has the correct permissions set.

[W234] warning - smart-restore parse error ‘%s’ on line ‘%s’
An error occurred while parsing your /etc/smartrestore file.

[W235] warning - problem creating archive catalog: filename
BRU could create its archive catalog file in the given directory specified in the GLOBAL BRUTAB BRUTEMP=directory

[W236] *** OBSOLETE MEGSSAGE NUMBER ***

[W237] *** OBSOLETE MEGSSAGE NUMBER ***

[E238] error - invalid -Q argument: “%s”
The argument that you passed with the -Q option is not valid. Arguments for -Q must immediately follow the -Q (i.e.: -QL) and be separated from the other options on the command line by at least one white space character.

[E239] error - invalid -U argument: “%s”
The only arguments for -U are numeric (0, 1, 2, etc).

[E240] error - unable to read, tape may be incompatible

[W241] warning - cannot translate “%s” to “%s”
Attempts to translate filenames during a restore were not allowed. This is probably a permissions problem.

[A242] enter label for volume %d:

[E243] error - previous UNMOUNTCMD on device “%s” failed

[W244] warning - left %d temporary files, check removelog file “%s”
During a restore, BRU ran into a number of open/in use files. These files were copied to a temporary directory and the tape version was restored. You may remove the temporary files by running the shell script displayed.

[I245] “%s”: skipped file, %s
The file listed was skipped in this operation because of the reason given.

Others in this Category
document Getting "Errno = 24, Too many open files" while performing a restore operation
document Correcting "Error: (0x05:0x3B0D) Medium destination element full" error messages
document brufilter: [E145] Streaming Checksum Error at Block...



RSS
Powered by KnowledgebasePublisher
Page Load Time: 0.114334 seconds / 114.334 milliseconds.
Page File Size: 130241 bytes.