Man page of advfs_err
Section: Devices and Network Interfaces (4)
Return to Main Contents
advfs_err - Lists and describes error messages
list provides the error number and a brief description of the error:
Out of memory.
The access structure handle is out of range.
This is an internal AdvFS error that occurs when an AdvFS routine fails
due to the domain already being paniced. The error propagates to the user
The volume is already in use by a domain.
The specified volume index is not a valid index in the domain.
The specified domain does not exist.
The bitfile does not exist.
The maximum number of file domains are active; cannot activate another
The specified domain handle is not valid.
The specified file page is not allocated and does not exist.
An advfs internal error when opening a file causes file storage to be
The file tag is not what was expected.
Out of extents to describe disk blocks.
The domain is out of disk space.
The requested function is not currently supported.
Invalid parameters were passed to the kernel. The likely cause is that
the command or utility belongs to a previous version of the product, while
the system is running a later version.
The file metadata was not found.
Service class array overflow.
The disk service class does not match the service class array entry.
The requested service class does not exist.
There is an attempt to delete a service class that still has a disk
Invalid transaction identification.
Invalid parent transaction handle.
Transactions are nested too deeply.
Invalid transaction handle.
The storage descriptor for the storage requested is invalid.
The file system (advfs) ran out of memory.
A file descriptor could not be allocated. The system is most likely
out of disk space.
Attempt to add storage to a file at a specified page offset and the
page at that offset already exists.
Too many threads are reading the transaction log.
There was a failure during log initialization.
The number of volumes in
not match the number of volumes in the BMT.
There are no transactions in the log.
There is no more room for transactions in the log.
The log entry has an invalid LSN.
No such log entry exists.
An error occurred while creating the file domain transaction log, initializing
the file domain transaction log, or both. Since you cannot use the file domain,
you must recreate it.
The file domain is not active; it must be active to perform the requested
Some thread is still accessing the domain during domain activation.
Dirty buffers prevent the fileset from being dismounted.
The command or utility version does not match the advfs kernel version.
The volume has the wrong domain ID.
There is an error in finding the end of the log.
A file's primary mcell has a nonzero linkSegment.
Some of the disks listed in
directory for the file domain do not belong to the file domain. The
directory entry for this file domain is
You must have root privilege to perform the requested function.
Specified tag to use next already is in use.
The specified file domain already exists.
The specified fileset does not exist.
The specified bitfile set handle is invalid.
The maximum number of filesets are mounted. Cannot mount the fileset.
The fileset is active (mounted). The fileset must be inactive (unmounted)
to perform the requested function.
There is no more room on the disks in the selected service class.
The file domain volume is an invalid device.
The file system (advfs) is not installed or it is installed but the
new kernel (vmunix) is not currently running; in the latter case, you need
to reboot the system to complete the advfs installation.
The file set is read only.
The specified fileset has the maximum number of clone filesets. You
cannot create another clone fileset.
The clone file is no longer correct due to running out of disk space
during a copy on write.
The original fileset has a clone fileset. The original fileset must
not have a clone fileset to perform the requested function.
The number of files in the fileset has exceeded the quota.
The number of disk blocks used by a fileset has exceeded the quota.
The quota type is not enabled.
I/O error detected.
Out of memory.
The fileset already exists.
You cannot create a clone fileset from a clone fileset.
Permission denied for the requested function.
During migration, a disk block offset in an extent is not page aligned.
An attempt to migrate a sparse file page range and all the pages in
the range do not exist.
The user, who is not the owner of the AdvFS resource, has attempted
an AdvFS operation, such as changing an AdvFS fileset name.
An attempt to migrate a file failed because another thread is already
migrating the file. Only one active migrate is allowed for a specified file.
The installed version of advfs is not compatible with the on-disk file
The on-disk file domain structures are invalid.
The page offset specified for the file is within a sparse file hole.
The maximum number of volumes per domain has been reached.
The file system (advfs) cannot generate the path name of a file because
the original path name has been deleted.
A trashcan operation was attempted on a non-advfs directory.
A user attempted to use a non-advfs directory for a trashcan.
A user attempted to attach a directory to itself as a trashcan.
A user attempted to attach a trashcan to a directory in a different
fileset. A trashcan must be in the same fileset as the directory.
The specified disks do not contain a valid advfs file domain.
An advfs internal error when opening a file causes the file storage
to be inaccessible.
The file domain contains no volumes.
There is a corrupted page in the tag directory.
A request to switch log volumes was made to a domain that is in the
process of switching log volumes.
A user attempted to remove
a trashcan from a directory that has no trashcan.
The quota type is
An attempt to remove a volume failed because the contents of the inode
table could not be moved off of the volume.
An attempt to remove a volume failed because the
tag directory is located on the specified volume and could
not be moved off of the volume.
An attempt to remove a volume failed because the log is located on the
specified volume and could not be moved off of the volume.
The selected disk is not in the requested service class.
The request call to lgr_flush_start would block.
An attempt to stripe a file that is already striped.
An attempt to migrate a clone but the clone has no storage of its own.
The specified page range is not valid.
A migrate operation has been aborted by another thread. For example,
a remove volume operation can cause a file's migrate to abort.
A remove volume operation on a volume in the specified domain is already
active. There can only be one active remove volume operation per domain.
- SEE ALSO
This document was created by
using the manual pages.
Time: 02:40:08 GMT, October 02, 2010