Enstore Library Manager Queues Help

Overview

Enstore Library Manager Queues gives detailed information about the internal queues and status of the library manager. These queues include an element for each write or read job that is currently being worked on or is pending. In addition, a summary of non-idle and non-active movers is given at the end. Idle movers are those that are waiting for work. Active movers are those that are working on reading or writing a file (this includes mounting and seeking operations). This page will automatically refresh, based on the value listed in the inquisitor section of the configuration file. It is created by the inquisitor, and includes the time/date when it was last updated in its upper right hand corner.

Status

The status of the library manager as reported on the Server Page is included here as well.

Suspect Volumes

A library manager will mark a volume as suspect with respect to a certain mover if the mover encounters an error while accessing that volume. The suspect volume list on this page includes each volume for which this has happened, followed by a list of the movers that reported an error for that volume.

Reads

This is the list of files in the library manager internal queue that are to be read from Enstore. Each file corresponds to an encp job. The files are sorted by volume, and within the volumes, are sorted by priority. The volumes themselves are sorted by priority. Here is an example -

EFB000	[at DD42.mover]	fndad	/neo/data/a_data_file	(CurPri : 1 File : 14)
		fndad	/neo/data/another_data_file	(CurPri : 1 File : 15)
		fndad	/neo/data/yet_another_data_file	(CurPri : 1 File : 17)
EFB001		fndad2	/neo/data/a_data2_file	(CurPri : 1 File : 15)
		fndad2	/neo/data/a_pending_data_file	(CurPri : 1 File : 15)

In this example, the volume labeled EFB000, has 3 files that users want to read from it. The first file, at position 14, is currently being read bu mover DD42.mover. The other 2 are pending. The volume labeled EFB001, has 2 files on it to be read, both of which are waiting for an available mover. The CurPri value is the current priority of the file read.

NOTE: Only the last 70 characters of the filename are displayed.

Writes

This is the list of files in the library manager internal queue that are to be written to Enstore. Each file corresponds to an encp job. The files are sorted by file family, and within the file family list, are sorted by priority. The file families themselves are sorted by priority. Here is an example -

file_family1	[at DD23.mover]	fndad2	/neo/data2/write_file_here	(CurPri : 1 FFWidth : 2)
	[at DD24.mover]	fndad2	/neo/data2/write_different_file_here	(CurPri : 1 FFWidth : 2)
file_family2	[at DD25.mover]	fndad	/neo/data2/another_file	(CurPri : 1 FFWidth : 2)
		fndad	/neo/data2/another_different_file	(CurPri : 1 FFWidth : 2)
file_family3		fndad1	/neo/data2/write_this_file	(CurPri : 1 FFWidth : 1)

In this example the file family file_family1, has 2 files currently being written to Enstore using movers DD23.mover and DD24.mover. The file family width for this file_family is 2, so that is the maximum number of writes that can be concurrent.
File family file_family2, also has 2 files to be written, one is being written now by mover DD25.mover. The other file is pending and is waiting for a free mover to be able to write it. Notice that this file families width is 2. There are many reasons why the second job is still pending, such as -

All movers are busy
The file was just submitted and will soon be given to an IDLE mover
A file is being read from a volume which belongs to this file family and the volume is not full. This volume will also count against the file family width because it is being read and is not full. Thus there would be 2 volumes mounted for this file family that could be written to and the second write job will not be given to a mover until one of the other 2 volumes is no longer being accessed.

File family file_family3, has 1 file pending (waiting to be written) for any of the reasons as discussed above.

The mechanism for giving jobs to IDLE movers is very complex and takes into account many more factors than are listed here.

Additional Movers

Any movers that are in one of the following states are listed here -

CLEANING
DISMOUNT_WAIT
ERROR
HAVE_BOUND
OFFLINE

This includes movers that are not currently waiting for a job (IDLE) or busy working on a job (SETUP, MOUNT_WAIT, SEEK, ACTIVE). The following information is listed for the mover -

Additional Mover	State	Volume	File Family
Mover name	Mover internal state	Volume Label of volume in drive	File family of the volume

Legal Notices

Last modified: Thu Mar 21 11:02:00 CST 2002