iXOS-JUKEMAN 2.2 User Manual Pre.12/97 iXOS Software AG • Technopark • Bretonischer Ring 12 • D-85630 Grasbrunn Tel. +49 (89) 46005-0 • Fax +49 (89) 46005-199 • email: office@munich.ixos.
Impressum ImpressumiXOS-JUKEMAN 2.2 User Manual Pre.12/97 Copyright 1997 iXOS Software AG All rights reserved, including those regarding reproduction, copying or other use or communication of the contents of this document or parts thereof. No part of this publication may be reproduced, transmitted to third parties, processed using electronic retrieval systems, copied, distributed or used for public demonstration in any form whatsoever without the written consent of iXOS Software AG.
Contents Contents 1 Introduction............................................................. 9 1.1 About this manual ............................................................................ 9 1.1.1 Software release and further information................................ 9 1.1.2 Structure of this manual........................................................ 11 1.2 Conventions ................................................................................... 12 1.3 iXOS-JUKEMAN — an overview.........
Contents 3.1 Introduction ....................................................................................29 3.2 Set up license keys ........................................................................31 3.2.1 Why do I need license keys? ................................................31 3.2.2 How do I get license keys? ...................................................31 3.2.3 How to enter license keys .....................................................34 3.3 Set up caches and buffers..........
Contents 4.4 Modifying the set-up....................................................................... 90 4.4.1 Change buffers and caches.................................................. 90 4.4.2 Add new devices................................................................... 91 4.4.3 Remove devices ................................................................... 92 4.4.4 Change views ....................................................................... 94 4.5 Network administration..............
Contents 5.10 DSM Terastore Jukeboxen.........................................................172 5.11 ELMS DVL..................................................................................173 5.12 Grundig GMS 1035 ....................................................................174 5.13 Grundig GMS 3200 ....................................................................175 5.14 Grundig GMS 3280 ....................................................................176 5.15 HP WORM/MO.................
Contents 5.39 Sony CDZ-R360 CD Jukebox .................................................... 204 5.40 Sony-CDL-2?00-?? CD Jukeboxen............................................ 205 5.41 Standard-SCSI2-Jukeboxen ...................................................... 206 5.42 Tower-Jukeboxen ohne LUN-Support........................................ 207 5.43 Einzellaufwerke.......................................................................... 208 5.44 Medien-Abbilder auf Festplatten..........................
Contents 11 Index .................................................................. 273 8 iXOS-JUKEMAN 2.2 User Manual Pre.
About this manual 1 Introduction 1.1 About this manual This manual covers the installation, set-up and usage of iXOS-JUKEMAN, a server software product for optical media. An introduction into the features and possibilities of the software can be found in the section “iXOSJUKEMAN — an overview” on page 13. 1.1.1 Software release and further information Covered in this manual is the release iXOS-JUKEMAN version 2.2. The latest release can always be found on our web server: http://www.jukeman.
Introduction New features in version 2.
About this manual 1.1.2 Structure of this manual Overview of the software: • “iXOS-JUKEMAN — an overview” on page 13. This section is recommended for first time users, who want to discover the possibilities and concepts of iXOS-JUKEMAN. First time installation and set-up: • “Installation” on page 21. • “Setting up iXOS-JUKEMAN” on page 29. These sections are required for first time installation and set-up of iXOS-JUKEMAN.
Introduction 1.2 Conventions The following conceptual and typographic conventions are used in this manual: Conceptual conventions: • Disk: iXOS-JUKEMAN supports all kinds of optical media: CDs, CD-Rs, PDs, MOs and WORMs which are generally referred to as disks in this manual. • GUI: The graphical user interface provides an easy way to administer iXOS-JUKEMAN on Windows NT. Sections dealing specifically with this way of administration are headed “GUI”.
iXOS-JUKEMAN — an overview 1.3 iXOS-JUKEMAN — an overview iXOS-JUKEMAN is the leading software product for managing jukeboxes, drives, and recorders for optical disks. It provides simple and efficient access to optical storage devices with unrivaled performance and flexibility. Simplicity iXOS-JUKEMAN presents all available disks as a standard file system, completely hiding the jukeboxes.
Introduction UNIX Windows Disks OS/2 Macintosh 1.3.1 Main components iXOS-JUKEMAN consists of a file system server and a CD writer. The server provides native file system support for multiple client types, and allows users to view CDs in their preferred file system format. It accesses real hardware devices and hides them completely by presenting an abstract hierarchical file system. It caches files and directories, optimizes access to CDs and jukeboxes, and minimizes jukebox movements.
iXOS-JUKEMAN — an overview NT network support NFS iXOS file system for NT iXOS file system server iXOS writer software iXOS generic SCSI driver hardware devices The server The iXOS-JUKEMAN server controls jukeboxes, disk drives, and the disks they contain. The server combines all disks in a single file system in which each disk is a subdirectory of the root directory and the jukeboxes are hidden. UNIX clients access the server’s file systems via NFS.
Introduction The writer The iXOS-JUKEMAN writer can send either ISO 9660 file systems or raw data to a disk recorder. Moreover, Rock Ridge attributes or the Joliet format can be used. The writer accepts data from a pre-mastered file, a raw partition, a disk drive, or from a pipe. The writer’s preview mode can be used to test the writing process before you start, and the verify option allows the CD to be verified immediately after it is written.
iXOS-JUKEMAN — an overview Table 1: Supported jukeboxes Manufactor Type Discs Drives Details see page ASM ASM CDR???? 100-1563 1-44 164 Cope Tower 6-7 6-7 165 Cygnet Infinidisc/Infiniwriter 250/500 2, 4, 6, 8 166 Cygnet ID100 100 1-4 167 Denon DRD-1408 200 2 168 DISC D??? 238-1478 18-48 169 DISC DA***.
Introduction Manufactor Type Discs Drives Details see page Plasmon CD150J 150 4 200 Plasmon D-Series 120/240 2/4/6 199 Plextor MegaPlex 200 2 201 Plextor PX-J2200 200 2 201 Smart and Friendly CDJ 7004 7 1 202 Smart and Friendly CDJ 4008 4 1 203 Sony CDZ-R360 360 2 204 Sony CDL-2?00-?? 125 (225) 2-4 205 any single drive 1 1 208 - image on hard disk - - 209 Table 2: Supported CD recorders Manufactor Type IFS* HP SureStore 4020i yes JVC XR-W1001 J
iXOS-JUKEMAN — an overview Manufactor Type IFS* Ricoh RS-9200CD Ricoh RS-9200GD Sony CDU920S Sony CDU924S Teac CD-R50S-000 Teac CD-R55S Yamaha CDE/CDR100 yes Yamaha CDR400(c,t) yes *IFS = Incremental file system, allows track-by-track writing of disks Due to upward compatability of the SCSI command set other recorders of the listed manufactors should also work with cdglow. iXOS-JUKEMAN 2.2 User Manual Pre.
Introduction 2 Installation 2.1 Introduction This chapter covers the installation of iXOS-JUKEMAN on Windows NT and UNIX hosts. A full installation is performed on the jukebox server. In addition the administration client can be installed on other hosts to allow remote administration of the iXOS-JUKEMAN server. Note: To set up and use the software right after installation, the devices to be controlled by iXOS-JUKEMAN should be connected and operational.
Installation 2.2 Requirements 2.2.1 Supported operating systems iXOS-JUKEMAN runs with the following operating systems: • AIX 4.* • DEC UNIX 4.0 (Alpha processor) • IRIX 6.2, 6.4 • HP-UX 10.* • Windows NT 3.51, 4.0 (with Alpha or Intel processor) • Solaris 2.4, 2.5, 2.51, 2.6 An updated list can be ordered from support@europe.jukeman.com. 2.2.2 System requirements • At least 32 MB memory, 64 MB recommended for burning disks. • At least one SCSI controller.
Windows NT installation 2.3 Windows NT installation The installation program for Windows NT copies files to a directory on your hard disk, installs iXOS-JUKEMAN services and sets up the registry entries. Before you begin installation, log on as administrator or a super user. Start the program jukeman.exe on the iXOS-JUKEMAN CD-ROM. The following dialog will open: In this set-up dialog, specify where you want to install the iXOSJUKEMAN user programs. (The default is %SystemDrive%\jukeman.
Installation lems and undesired effects on the JUKEMAN server. A checkmark by Disable Autorun Feature will assure that no autorun files will be started on the server. This feature can also be configured in the registry (regedt32.exe): autorun feature You will probably want to install all these items. If you install the administration client on other hosts the iXOS-JUKEMAN server can be administered through the network. The administration client will also run on Windows 95.
UNIX installation 2.4 UNIX installation Before you begin installation log on as root. All the files needed for installation can be found on the iXOS-JUKEMAN CD-ROM or downloaded from the world wide web (see page 9). To download, follow the instructions on the web pages. Important files to be downloaded are the operating system-specific file and the file with configuration examples ('examples.tz'). The following table lists the operating system-specific files. These files are compressed 'tar' files.
Installation cp solaris.tz /jukeman/solaris.tar.Z cp examples.tz /jukeman/examples.tar.Z cd /jukeman zcat solaris.tar.Z | tar xvf Now you have all the files except license files, device descriptions and configuration. If you wish to update an earlier version, copy the old configuration files (server.cfg, *.dev, *.sav, *.lic) and the database volumes to the new target directory.
UNIX installation For HP-UX 10.* change the permissions for both the cdadm and the inquiry command: chown root cdadm inquiry chmod u+s cdadm inquiry To set up the software, see “Setting up iXOS-JUKEMAN” on page 29. If you just want to use the writer software you do not have to set up anything else. The software is described in the section “Burning disks” on page 133. If you have already received a license key for the writer software from your distributor, enter it in the file writer.
Introduction 3 Setting up iXOS-JUKEMAN 3.1 Introduction iXOS-JUKEMAN must be set up before you can start and use the software. The following sections will tell you how to: • Set up license keys. This section may be skipped if you have no license keys and want to test the software in demo mode. • Set up caches and buffers. Setting up a directory cache will improve the overall performance of the server. Setting up this cache pays off as soon as a new jukebox is attached to the server. • Set up devices.
Setting up iXOS-JUKEMAN There are two ways the set-up can be performed: 1. With the GUI on Windows NT. The administation client must be started. This can be done from the NT “Start” menu ([START][PROGRAMS]-[IXOS-JUKEMAN]-JUKEMAN ADMINISTRATION or by running “jukeboy” from the JUKEMAN directory). The corresponding sections are entitled GUI. 2. By editing configuration files on Windows NT and UNIX. Sections with this set-up method are entitled CLI (Command Line Interface).
Set up license keys 3.2 Set up license keys 3.2.1 Why do I need license keys? Valid license keys allow you to take advantage of all the features of iXOSJUKEMAN. There are separate license files for the server and the writer software, which specify a possible license time-out restriction and the number of disks the server will be allowed to handle. The license files are: • server.lic contains the number of supported physical disks. • writer.
Setting up iXOS-JUKEMAN IRIX: /sbin/sysinfo -s NT: either the IP address in the result of ‘ipconfig’or the network adapter address, which can be determined by the last entry of the “Workstation active on” line of the result of net config workstation. /usr/ucb/hostid Solaris: The host ID also appears at the top of the file named logfile.txt in “Your key for a license order:”. For an NT host with more than one IP address or network adapter any of the addresses can be used to obtain a valid license key.
Setting up iXOS-JUKEMAN 3.2.3 How to enter license keys GUI Windows NT Select [SERVICE]-LICENCE KEYS: In this dialog the license keys for the server and the writer are entered independently. Major Version Number: Should be '2' for all versions 2.xx of iXOSJUKEMAN. Server license for _ volumes: Enter the number of supported physical disks. License expires...: For an evaluation license, deselect 'never' and enter the time-out date. License key is: Enter your 8 character license key.
Set up license keys CLI UNIX, Windows NT Open one of the following files server.lic or writer.lic with a text editor. The default files look like this: server.lic: writer.lic: unlimited license version=2 volumes=250 version=2 writer license=justdemo license=justdemo time-out license version=2 volumes=250 version=2 writer timeout=1997/06/13 timeout=1997/06/13 license=justdemo license=justdemo The settings printed in bold must be changed to match your license.
Setting up iXOS-JUKEMAN 3.3 Set up caches and buffers Caches speed up access to frequently used data. With iXOS-JUKEMAN you can set up both a directory and a data cache. Caches on your hard disk are not required to run iXOS-JUKEMAN, since it always holds a directory and data cache in RAM. For a large number of disks, however, it is recommended to set up at least a directory cache. In addition, iXOS-JUKEMAN supports incremental writing to disks with the incremental file system.
Set up caches and buffers 2. If a new disk is inserted into a drive, iXOS-JUKEMAN checks to see if the root directory is in the cache. If it is not, the parameter autodc (see section “Server parameters” on page 123) determines what happens next. If set to 0, no caching is performed. If set to 1, caching is performed only if a permanent hard disk directory cache is configured. When set to 2, JUKEMAN will cache the entire directory structure.
Setting up iXOS-JUKEMAN 3.3.2 How to set up the directory cache GUI Windows NT Select [CONFIGURATION]-BUFFERS AND CACHES: If the server is running, iXOS-JUKEMAN asks you to shut it down. Click [YES] to stop it. 1. Deselect No directory cache. 2. Click [DEFAULT] for the default settings. 3. Enter a file name for the cache in the File name field. Please note that for security reasons the cache file can be created in the JUKEMAN directory or its subdirectories only.
Set up caches and buffers CLI Note: UNIX, Windows NT The file server.cfg must be modified for this task. A detailed description of the file can be found in “Configuration file server.cfg” on page 237. It is recommended that you make a backup copy of the file before editing it. 1. Open the file “server.cfg” with a text editor. 2. Find the section “dircache { ... }”. If it does not exist, add the following lines to the end of the file: dircache { file { } size { } } 3.
Setting up iXOS-JUKEMAN 3.3.3 The data cache In addition to the directory cache, iXOS-JUKEMAN allows to set up a cyclic cache for regular data. All data accessed will also be stored in this cache. When the data is accessed again, it can be read directly from the data cache, so the disk does not have to be accessed. Being cyclic like the directory cache, when the data cache gets full old data will be replaced as soon as new data is accessed. The default size of the data cache is 2 MB in RAM.
Setting up iXOS-JUKEMAN 3.3.4 How to set up the data cache GUI Windows NT Select [CONFIGURATION]-BUFFERS AND CACHES: If the server is running, iXOS-JUKEMAN asks you to shut it down. Click [YES] to stop it. 1. Deselect No data cache. 2. Click [DEFAULT] for the default settings. 3. Enter a file name for the cache in the File name field. Please note that for security reasons the cache file can be created in the JUKEMAN directory or its subdirectories only.
Set up caches and buffers CLI Note: UNIX, Windows NT The file server.cfg must be modified for this task. A detailed description of the file can be found in “Configuration file server.cfg” on page 237. It is recommended that you make a backup copy of the file before editing it. 1. Open the file “server.cfg” with a text editor. 2. Find the section “regcache { ... }”. If it does not exist, add the following lines to the end of the file: regcache { file { } size { } } 3.
Setting up iXOS-JUKEMAN 3.3.5 The IFS buffer (incremental file system) With iXOS-JUKEMAN you can write a disk incrementally. After initialization you can copy or move files to a disk as easily as you would move them to your hard disk. The only difference is that you have to flush the IFS buffer to actually burn the buffered files to disk. Note that you require a valid license key if the writer is to burn more than 128 MB to a disk.
Setting up iXOS-JUKEMAN 3.3.6 How to set up the IFS buffer GUI Windows NT Select [CONFIGURATION]-BUFFERS AND CACHES: If the server is running, iXOS-JUKEMAN asks you to shut it down. Click [YES] to stop it. 1. Deselect No incremental file system. 2. Click [DEFAULT] for the default settings. 3. Enter a file name for the buffer in the File name field. Please note, that for security reasons the cache file can be created in the JUKEMAN directory or its subdirectories only. 4.
Set up caches and buffers CLI Note: UNIX, Windows NT The file server.cfg must be modified for this task. A detailed description of the file can be found in “Configuration file server.cfg” on page 237. It is recommended that you make a backup copy of the file before editing it. iXOS-JUKEMAN 2.2 supports more than one IFS buffer (see “IFS with several independent buffers” on page 243). To set up a single IFS buffer do the following: 1. Open the file “server.cfg” with a text editor. 2.
Setting up iXOS-JUKEMAN 3.4 Set up devices Each device controlled by the server requires a description file that specifies the device type, the SCSI address and properties of the drive, and the SCSI address or RS232 address of the robot (changing mechanism). The file also specifies which storage slots the server should use (default is all slots) and an optional file that stores the contents of the slots.
Set up devices SCSI devices and device names In UNIX and NT, each device is represented by a device name, which is a path in the root file system tree. NT hides the devices, but iXOS-JUKEMAN makes the names visible. The SCSI ID x on bus y of controller z is represented by the path \\.\pzbytx. So if you have a PCI bus and put Adaptec twin adapters AHA 3940 into bus slots 0 to 2, you will have 6 SCSI buses, and ID 4 on bus 1 of adapter 2 is represented as \\.\p2b1t4. Each enumeration begins with 0.
Setting up iXOS-JUKEMAN The first line gives the drive type, the second line gives the firmware version. 0000000 Can't open \\.\p0b0t5 occurs if the driver is not running, the path is wrong, the device does not work, the termination is wrong, or the cable is bad. The device may also be unknown if it was not running when you booted the system. If you do not know the paths that represent your devices, call scsidevs It returns a complete list of all known and working SCSI devices.
Set up devices AIX uses a multiplex driver: You can use the devices but not see them. If you issue the following command: ls -l /dev/iXOS_SCSI? the output should look like this: lrwxrwxrwx 1 root system 13 Oct 22 14:22 /dev/iXOS_SCSI0-> genscsi/scsi0 lrwxrwxrwx 1 root system 13 Oct 22 14:22 /dev/iXOS_SCSI1 -> genscsi/scsi1 This shows that the files are in fact symbolic links to our generic SCSI driver. You can use the csh expansion mechanism ‘{...}’to list the device paths created by the driver.
Setting up iXOS-JUKEMAN With the following you can find out which IDs and LUNs are occupied by which devices: inquiry /dev/iXOS_SCSI{0,1,2,3,4}/{0,1,2,3,4,5,6},0 IDs and LUNs that are not used return “SCSI-Error in 00 - TEST UNIT READY”) 3.4.3 Serial lines For several jukebox types, the robot is controlled through a serial line, which allows you to save a SCSI ID.
Set up devices through the server. For Windows NT, this section may be skipped, as you can use the GUI to generate the device description files. 3.4.4 Device description files A device description file contains lines in the format =. Some keys must be specified for all devices, others must be specified only for certain types. Device type set-up The most important parameter is the device type: device=. The supported Jukeboxes and their type are listed in the following table.
Setting up iXOS-JUKEMAN Type Jukeboxes pioneer500 Pioneer DRM-5004x plasmond Plasmon D-Series plextor200 Plextor MegaPlex (also known as PX-J2200) ps_lf_j Panasonic LF-J-50/100/200 satellite NSM Satellite scsi2 Standard SCSI-2 jukeboxes single SCSI single drives sony_cdl Sony CDL-2?00-?? sony_cdz Sony CDZ-R360 standard NSM Mercury 20s, 31s and 40s, Plasmon CD150J, ASM Jukeboxen, Grundig M35 tower Cope Tower worm WORM and MO jukeboxes Drive set-up Each device description file must
Set up devices 3. For a recorder drive you want to use for incremental writing from the file system, choose the syntax drive=* (see also “Burning disks incrementally” on page 151). 4. In all other cases, use the syntax drive=… . For example, if you want the server to control a single drive that the generic SCSI driver presents as \\.\p0b0t4 or /dev/iXOS_SCSI0/4 the device description file should look like this: Windows NT device=single drive=\\.
Setting up iXOS-JUKEMAN If not otherwise specified in the device description file, all slots will be used. You can specify a few disks by adding a line such as disks=1-3 or disks=1,2,4-6. The slots can be specified using the following syntax: - no slot 7 slot 7 3,6,40 slots 3, 6 and 40 3-7 slots 3 through 7 2,20-45 slot 2, and slots 20 through 45 Save file set-up When the server attaches a device, it inspects only the specified disks.
Set up devices device=pioneer18 drive=\\.\p0b0t3 robot=\\.\p0b0t3,1 disks=1-9 device=pioneer18 drive=/dev/iXOS_SCSI0/3 robot=/dev/iXOS_SCSI0/3,1 disks=1-9 For the “kubik”, the robot uses a serial interface. The device description file looks like this: device=kubik drive=\\.\p0b0t1 drive=\\.\p0b0t2 drive=\\.\p0b0t3 drive=\\.
Setting up iXOS-JUKEMAN 58 iXOS-JUKEMAN 2.2 User Manual Pre.
Setting up iXOS-JUKEMAN 3.4.6 How to set up devices GUI Windows NT Select [DEVICES]-NEW... or click [NEW...]: start-up behavor device name device type used slots (default: all slots) (see page 53) robot (see page 56) drives (see page 54) Entering the device name Type a device name into the Name field. This name may be 8 characters long. This will also be the name of the device description file and the save file that will be created in the JUKEMAN directory (with the extension .dev/.sav).
Set up devices For example, all drives that could not be mapped properly appear as “undefined” in the drives list. SCSI jukeboxes and changers SCSI drives, towers, recorders jukeboxes on serial lines Select all device types you want the wizard to check for and click [DETECT]. Detection may take longer if the serial lines are searched for jukeboxes. Click [DETECT] to go on. If the serial lines will be searched for devices, the server needs to be stopped. Click [YES]. iXOS-JUKEMAN 2.2 User Manual Pre.
Setting up iXOS-JUKEMAN From the list of detected devices, select the one you wish to configure and click [CONFIGURE]. The device wizard enters the values into the appropriate fields automatically. Attach devices automatically Select “Attach at Server Start” if the device should be attached automatically at server start-up. Using only several slots Enter the slots to be used in the “Use only these Slots” field. See page 56 for the syntax. If this field is left blank, all slots will be used.
Set up devices CD or Sony CDZ-R360), all possible selections will be listed in this field. If the robot is a serial line (as with Kubik- or NSM jukeboxes), the available serial interfaces and Robot IDs will be listed. See section “Robot set-up” on page 56. Select the appropriate robot from the list. If no robot is to be specified (e. g., Pioneer 6), this field is greyed out. Drives/Files Each drive of a jukebox (or one or more files for a hard disk image) must be specified. Click [ADD...
Setting up iXOS-JUKEMAN • Not used by file system can be selected for drives that will be dedicated to writing disks (see “Production of CDs in jukeboxes” on page 141). • In all other cases select Normal use by file system. These drive properties can be changed at a later time by doubleclicking on a drive in the device definition dialog. Click [OK] to define the drive. Click [CANCEL] to discard the changes. Confirming or discarding the device set-up Click [OK] to confirm the device set-up.
Set up devices CLI UNIX, Windows NT Use a text editor to create a file “.dev” in the JUKEMAN directory. Choose a that gives a hint about the configured device (e. g., mercury or tower). Enter the following lines in the file: device= is the device type of device to be configured. See “Table 3 - Device types for all supported jukeboxes” on page 53. drive= Each drive must be specified with a line of this format.
Setting up iXOS-JUKEMAN If all lines are entered, save the file “.dev”. The section “Attach devices automatically” on page 102 tells you how to configure the server to attach one or more devices automatically at startup. If you have created a device description file named device.dev, the device can be attached with the command cdadm attach device The server will inspect the specified slots and present the disks to the views of the file system.
Set up views 3.5 Set up views The views concept allows you to set up the iXOS-JUKEMAN file system to your liking. This way a structure can be built to present all the disks clearly to network users. For instance, if you had hardware managing 700 disks and all these disks would be visible as subdirectories to a single root directory, the clients accessing the data might be presented with problems to find the desired disks.
Setting up iXOS-JUKEMAN any case by explicitly renaming volume names any name up to 32 characters long can be chosen. The Rock Ridge format displays file and directory names in ISO 9660 format, with regard to the Rock Ridge extensions (if available). These additions to ISO 9660 allow UNIX file names to be presented in ISO 9660 file systems. The Rock Ridge extensions may also contain UNIX file permissions. In High Sierra format the file and directory names will be presented exactly as stored on disk.
Set up views Table 4 - Disk set syntax Char. Meaning Example possible disks (e. g.) ? any single character ix?s ixas, ixos, ixks.. * any string ix*s [...] list of alternatives [abc]horn [-] range of characters [a-m]horn ixs, ixmas, ixotic... ahorn, bhorn, chorn ahorn, ..., mhorn [^] restricted characters [^d]* {cow, alternative strings mick}* {...,. ..,... } all starting without “d” all starting with cow or mick Summary: • iXOS-JUKEMAN allows to set up a tree of views.
Setting up iXOS-JUKEMAN Disks pc rr rr view_1 view_2 view_3 ixos97.cd1 ix_nix_l.isa workbone.rrt iXBackup-Templates_1_97 iXOS97.cd1 iX_NIX_LISA-96 iX-database.work rr hs view_3a view_3b iXOS_Training.97 * (all disks available) Figure 1 - Example for different views In server.cfg the description for the above views set-up would look like this: views { list { view_1 view_2 view_3 } roots { view_1 { discs { ixos97.cd1 usenix_l.isa workbone.
Setting up iXOS-JUKEMAN 3.5.1 How to set up views GUI Windows NT Select [CONFIGURATION]-FILE SYSTEM VIEWS: The dialog shows the default views configuration. Using this dialog, new views may be added and configured, and existing views may be changed, renamed, or removed. By default, the 'Root' view is mapped to the drive letter Z: and contains two subviews 'views_pc' and 'views_rr' in the PC name format and the Rock Ridge name format, respectively.
Set up views new view and confirm with 'RETURN'. If a view is to contains subviews contains views must be selected for this view. Otherwise click contains volumes. Renaming a view: Select the corresponding view and click [RENAME], or double-click the view. Enter a new name and press 'RETURN'. Removing a view: Please note that all subviews will be lost, if a view is deleted. Select the appropriate view and click [REMOVE].
Setting up iXOS-JUKEMAN The administration client will save the views configuration in the file server.cfg. 74 iXOS-JUKEMAN 2.2 User Manual Pre.
Set up views CLI UNIX, Windows NT Note: The file server.cfg must be modified for this task. A detailed description of the file can be found in “Configuration file server.cfg” on page 237. It is recommended that you make a backup copy of the file before editing it. Open the file server.cfg with a text editor. The views are entered in the views { ... } section. The first parameter that must be specified is list { }, containing the names of all views on top level.
Setting up iXOS-JUKEMAN Suppose you wanted to export the following disk set: A view views_pc, containing all disks for PC clients in the name format pc, a view views_rr, containing all disks for UNIX clients in the name format rr and a view find_easier, containing two subviews. One subview should contain all the disks starting with the letters a, b, c, ..., m in PC format and leave out all disks starting with archive.
Intregrate iXOS-JUKEMAN into the network 3.6 Intregrate iXOS-JUKEMAN into the network Until now you have: • installed iXOS-JUKEMAN • entered license keys • set up caches and buffers • set up devices • set up views. This section teaches you the last few steps necessary to enable the clients to access the disks when the server is started. 3.6.1 The server side iXOS-JUKEMAN on Windows NT The NT version of iXOS-JUKEMAN fits many different environments, including those that are mixed.
Setting up iXOS-JUKEMAN All views you set up in addition must be explicitly shared. This can be easily done with the Windows NT Explorer. For example, if you configured a view which is mapped to drive letter W:: In the Explorer, move the mouse pointer to the drive letter or directory you wish to share and click the right mouse button. Select [SHARING] from the pop-up menu. A dialog will pop up in which the drive letter or directory can be shared to the clients.
Intregrate iXOS-JUKEMAN into the network iXOS-JUKEMAN on UNIX On UNIX iXOS-JUKEMAN cooperates with the standard NFS server. If no NFS is running, the set-up of the file system is finished. If NFS is running, you must set up the standard rpc.mountd daemon to cooperate with the server. rpc.mountd monitors all file systems, including that of iXOS-JUKEMAN. If clients mount a network file system they ask rpc.mountd for a root file handle.
Setting up iXOS-JUKEMAN /views_pc -ro /views_rr donald daisy garfield localhost These lines will export /views_pc read-only to all hosts and /views_rr to the hosts donald, daisy, garfield and the server itself. Please keep in mind that the entry localhost is mandatory when specifying certain hosts. On Solaris the exported file systems are listed in the file /etc/dfs/dfstab.
Intregrate iXOS-JUKEMAN into the network NFS Clients (UNIX, NT) NFS clients, e. g., UNIX clients, can mount the standard views :/views_pc or :/views_rr of a Windows NT JUKEMAN server. For example: mount -o timeo=99,retrans=14 jm_hostname:/views_pc /cds The disks can then be accessed from the directory /cds on the client. Both the UNIX and NT versions of iXOS-JUKEMAN support the NFS protocol.
Setting up iXOS-JUKEMAN mount -o port=4027,timeo=99,retrans=14,soft :/views_rr /cd mounts the server’s file system on the empty directory /cd of the client. Once this is done, all disks appear as subdirectories of /cd. The simple command ls -l /cd shows a list of all available disks. Depending on the operating system, some versions of mount require additional parameters, e. g., mount -F nfs -o port=.. or mount -f NFS,port=… . See man mount for details.
Intregrate iXOS-JUKEMAN into the network The retrans=14 option instructs the kernel’s NFS client to automatically retransmit a request 14 times before it gives up and the file system access that caused the NFS request fails. It makes sense to specify a high value because if several clients access different disks located in the same jukebox, the server must move these disks, and the last client must wait a long time.
Introduction 4 Using iXOS-JUKEMAN 4.1 Introduction This section is devided into taks described for both the GUI and the CLI: Section The server Starting iXOS-JUKEMAN Modifying the set-up Network administration Attach devices Detach devices Attach devices automatically Display statistics Manage disks Server parameters Burning disks/writing incrementally iXOS-JUKEMAN 2.2 User Manual Pre.
Using iXOS-JUKEMAN 4.2 The server The jukebox file server is the core of iXOS-JUKEMAN. It controls the devices, and replies to NFS requests and to requests from the iXOSJUKEMAN local file system for NT. The server and all the programs and files it needs are in the JUKEMAN directory. All paths described here are relative to the JUKEMAN directory. The server cdnfsd runs as a daemon and receives requests from NFS clients, from cdadm and from the iXOS-JUKEMAN native file system for NT. It creates logfile.
Starting iXOS-JUKEMAN 4.3 Starting iXOS-JUKEMAN 4.3.1 Windows NT: Starting the server On NT the services “iXOS Admin Server” and “iXOS Jukebox Daemon” will be started automatically when the server is installed followed by a reboot of the host. This behavior can be changed with the “Services” table from the “Control Panel”: Clicking [START] and [STOP] the selected service can be started and stopped (in that order).
Using iXOS-JUKEMAN NT Administration client Menu entries Meaning Page Start or stop the jukebox service Select a host for network administration ................ 96 Enter license keys ................................................. 34 Exit the administration client Set up views .......................................................... 72 Edit the volumes database ..................................112 Edit server parameters .........................................130 Set up buffers and caches ......
Starting iXOS-JUKEMAN The iXOS-JUKEMAN administration client is a graphical user interface (GUI) that can be run on any Windows NT or Windows 95 computer in the network. The network address of the host where iXOS-JUKEMAN is running is stored in the file “jukeboy.ini” in the %systemroot% directory. You can configure devices and views on the file system and insert and remove disks from a jukebox using the GUI.
Using iXOS-JUKEMAN 4.3.2 UNIX: In the JUKEMAN directory, call: ./cdnfsd You must be logged in as root. iXOS-JUKEMAN should display a message like this: Starting iXOS-JUKEMAN Version 2.2 Server, build 1007.12 Copyright 1991-1997 iXOS Software AG ... iXOS-JUKEMAN started The server starts up and exports the file systems. The exported file systems (e. g. /views_rr) can be mounted with NFS (even locally). The disks do not appear in the directories representing the views (e. g.
Modifying the set-up 4.4.2 Add new devices You can set up new devices at any time. Please note that the limit of licensed disks may be exceeded when you attach new devices to the server (see “Set up license keys” on page 31). Disks exceeding the limit appear as “- limit -” in the [CONTENTS] dialog or with “cdadm survey…”. These disks are not visible in the file system. Follow the instructions in “How to set up devices” on page 60.
Using iXOS-JUKEMAN 4.4.3 Remove devices GUI Windows NT 1. Select the corresponding device from the device list. 2. Click [DETACH] to detach the selected device. 3. Click [REMOVE] to remove the selected device. The device description file and the save file will be deleted. The names of the disks located in the removed device will remain in the volumes database of iXOS-JUKEMAN. The advantage is that any renamings will not be lost if the disks are made available again.
Modifying the set-up CLI UNIX, Windows NT 1. Change to the JUKEMAN directory. 2. Enter “cdadm detach ” to detach the device. is the name of the device to be removed. 3. Remove the corresponding device from the file server.cfg (see “Configuration file server.cfg” on page 213). To to this, open the file server.cfg. All devices are defined in the devices section.
Using iXOS-JUKEMAN 4.4.4 Change views Follow the instruction in “How to set up views” on page 72. If you change the views manually in the file server.cfg the changes can be made active with the command cdadm cvtree (see page 217) without having to stop the server. On UNIX, the corresponding directories must be created and exported as described in “Intregrate iXOS-JUKEMAN into the network” on page 77. 94 iXOS-JUKEMAN 2.2 User Manual Pre.
Using iXOS-JUKEMAN 4.5 Network administration GUI Windows NT The GUI communicates via TCP/IP (port 4072) with the Admin service, which must be running on the (NT) host where iXOS-JUKEMAN is running. In most cases, this will be the local host (the default), but since the GUI can run on any computer in the network, you can choose a particular host. Select [SERVICE]-SELECT HOST: 1. Enter the host name or IP address in the text field of the dialog.
Network administration CLI UNIX, Windows NT You can call the administration client cdadm with an optional parameter “h ”. If this parameter is specified the command will not be executed locally, but on the specified host. Example: cdadm -h jukeserver attach tower.dev will attach the device with the device description file tower.dev to the host “jukeserver”. iXOS-JUKEMAN 2.2 User Manual Pre.
Using iXOS-JUKEMAN 4.6 Attach devices GUI Windows NT 1. Select the corresponding device from the device list. 2. Click [ATTACH] to attach the device to the server. 98 iXOS-JUKEMAN 2.2 User Manual Pre.
Attach devices CLI UNIX, Windows NT 1. Change to the JUKEMAN directory. 2. Enter cdadm attach . is the name of the device description file. The extension .dev may be omitted. iXOS-JUKEMAN 2.2 User Manual Pre.
Using iXOS-JUKEMAN 4.7 Detach devices GUI Windows NT 1. Select the corresponding device from the device list. 2. Click [DETACH] to detach the selected device from the server. 100 iXOS-JUKEMAN 2.2 User Manual Pre.
Detach devices CLI UNIX, Windows NT 1. Change to the JUKEMAN directory. 2. Enter cdadm detach . is the name of the device description file. The extension .dev may be omitted. iXOS-JUKEMAN 2.2 User Manual Pre.
Using iXOS-JUKEMAN 4.8 Attach devices automatically Using the command cdadm (see section “Command line index” on page 213), devices can be attached or detached dynamically while the server is running. In addition, you may specify a list of devices to be attached automatically when the server starts up. The server will not respond to file system requests while devices are being attached automatically.
Attach devices automatically devices { list { mercury pioneer } mercury { startup { automatic } } pioneer { startup { manual } } } iXOS-JUKEMAN 2.2 User Manual Pre.
Using iXOS-JUKEMAN 4.9 Display statistics iXOS-JUKEMAN allows to print statistics about device and disk accesses. There are three types of statistics: • the amount of transferred data and disk moves concerning the disks in all controlled devices • the amount of transferred data and disk moves concerning the disks in a specific device • The amount of transferred data and disk moves concerning the disks in one device (summed up) The values are with regard to the running server process.
Display statistics GUI Windows NT [STATISTICS]-VOLUME STATISTICS: The following dialog will pop up: The dialog displays a list of all disks controlled by iXOS-JUKEMAN. Displayed are: • disk name (volume) • number of read accesses (reads) • MBs read (MBs) • number of moves of a disk into a drive (moves) The list can be sorted by any of the four columns (radio button sort by).
Using iXOS-JUKEMAN [STATISTICS]-DEVICE STATISTICS: The following dialog will pop up: The dialog displays a list of all disks controlled by iXOS-JUKEMAN. Displayed are: • device name (device) • number of read accesses (reads) • MBs read (MBs) • number of moves of a disk into a drive of the device (moves) The list can be sorted by any of the four columns (radio button sort by). 106 iXOS-JUKEMAN 2.2 User Manual Pre.
Display statistics [STATISTICS]-CD STATISTICS PER DEVICE: The following dialog will pop up: The dialog displays a list of all disks controlled by iXOS-JUKEMAN. Displayed are: • disk slot (slot) and disk name (CD) • number of read accesses (reads) • MBs read (MBs) • number of moves of a disk into a drive (moves) The list can be sorted by any of the four columns (radio button sort by).
Using iXOS-JUKEMAN CLI UNIX, Windows NT From the command line statistics can be printed with the command cdadm survey (see also page 229). The order of the parameters is: 1. What should be reported? 2. What should be displayed in the report? 3. Shall the report be contrained (e. g., just one device)? 4. Shall the output be sorted and by what criteria? The first two parameters are mandatory, the others are optional.
Display statistics General: +d device names of attached devices (to be more specific: the name of the device description file) +n Total number of slots of a device +s Slot number +i inode number in volumes database Disks: +m type of disk (CD-ROM, rewritable...
Using iXOS-JUKEMAN +w W+B (total amount of data for a disk) +F S-W (free space on physical disk) +f S-w (free space for further data) +T number of tracks written to a disk Statistics: +D amount of data (MBytes) read from a disk +-D like +D, but set all values to zero afterwards +P number of operations on a disk, i. e. read accesses with max.
Display statistics The latter prints information for all other devices (negative comparison). For a disk list, you can apply restrictions for all columns, even if a column is not selected. Examples: “cdadm survey -v +sip d=juke.dev” will print all disks of juke.dev. “cdadm survey -v +dsipr p=ixos96” will print the disk with the PC format name ixos96. Note: (t)csh and bash users must preceed ! with a backslash to avoid its usual function as History operator.
Using iXOS-JUKEMAN 4.10 Manage disks GUI Windows NT The [CONTENTS] dialog Select [CONTENTS] or [DEVICES]-CONTENTS. The dialog will display a list of all slots and their current contents. The disk names appear in the selected name format for standard disks. The following special labels may also appear: Lable -limit- -blank-badCD- -empty-nostd------x????????? 112 Meaning This label appears if the limit of licensed disks is exceeded. These disks will not be visible in the file system. Empty disk.
Manage disks This dialog lists all slots of the currently selected device. The list displays the slot number followed by the disk name in the selected name format. By default, the original name of the disk is displayed (Original). The name format can be selected with one of the radion buttons PC, RR, HS, and Original. Rename disks Note: iXOS-JUKEMAN 2.2 allows disks to be renamed using the operating system functions (e. g., Windows NT Explorer or UNIX mv command).
Using iXOS-JUKEMAN 3. Enter a new name for the desired name format. 4. Click [OK] to accept the changes. Click [CANCEL] to discard the changes. Insert/remove disks Depending on your type of jukebox (mail slot or not), the GUI offers two different buttons to change disks: The button [CHANGE CD] is available, if the jukebox does not have a mail slot to change disks. To change a disk in this type of jukebox, select the slots in which disks should be changed and click [CHANGE CD].
Manage disks will be scanned periodically for new disks (see server parameter dcheck in section “Server parameters” on page 123). Move disks to or from a drive If a disk is accessed by a client request it will be moved to a drive automatically. If you want to move a disk into a specific drive (e. g., a recorder) click [MOVE CD] and select the slot number and the drive: To move a disk from a drive back to its slot select “from Drive back to Slot” and select the drive.
Using iXOS-JUKEMAN [INCREMENTAL FS] The incremental file system is described in section “Burning disks incrementally” on page 151. The [VOLUMES] dialog Select [CONFIGURATION]-VOLUMES. This dialog displays the disk names of all disks known to iXOS-JUKEMAN (and the renamings). All disk names scanned by iXOS-JUKEMAN are stored in the internal volumes database, even if you remove disks from a jukebox or drive. Available disks are marked “+”, currently unavailable disks are marked “”.
Manage disks this before the name is actually deleted. To remove the disk names of all unavailable disks, click [DELETE ALL UNUSED VOLUMES]. iXOS-JUKEMAN 2.2 User Manual Pre.
Using iXOS-JUKEMAN CLI UNIX, Windows NT List disks You can display a list of all disks using the following command: cdadm survey -v +idsoprh The following columns are printed (see page 229 for a list of other columns): (1) Disk ID in the volumes database, (2) name of the device description file, (3) slot number, (4) original disk name, (5) pc name, (6) rr name, (7) hs name. The output will look similar to this: (1) 362 325 137 535 0 541 (2) tower.dev tower.dev tower.dev tower.dev tower.dev tower.
Manage disks Rename disks Note: iXOS-JUKEMAN 2.2 allows disks to be renamed using the operating system functions (e. g., Windows NT Explorer or UNIX mv command). The renaming takes place for the name format defined for the view. cdadm rename [[-] []] renames the disk from to for the specified name format which must be either pc, rr or hs (see “Set up views” on page 67). must be an existing disk name for , must not exist.
Using iXOS-JUKEMAN i) For single drives and drives in tower jukeboxes a disk change is very easy: Just insert the disks into or remove them from the drives. No interaction with the server is required. The server will check these drives for disk changes periodically (see parameter dcheck in “Server parameters” on page 123). The changed disks do not have to be tested anymore, as with earlier versions of iXOS-JUKEMAN.
Manage disks iii) The pioneer500 has a virtual mail slot which is in fact a position of the robot. The grundig35 has a mail slot which is hidden under an additional door. You can use all of the above commands, but with the additional switch -f (cdadm insert -f ... or cdadm remove -f ...). As soon as the command returns, the picker of the pioneer500 is in its change position, or the door of the grundig35 may be opened.
Using iXOS-JUKEMAN moves the disk from drive 3 back to its slot. Note that the drive must be active (not disabled by a drive=! line in the device description file) to be accessible for move commands (see “Drive set-up” on page 54). Test disks cdadm testcd The command testcd can be used to test the contents of slots, especially to make newly inserted disks known to the server. Example: cdadm testcd jb.
Server parameters 4.11 Server parameters You can change the server behavior using several parameters, though the default values are usually quite sensible. server.cfg override default values and command options override default values and server.cfg values. A few parameters can be changed dynamically while the server is running. See “Change server parameters” on page 130. 4.11.
Using iXOS-JUKEMAN fullvn=0 By default, disk names in the PC name format are converted to 8.3 in lower case. If fullvn is set to 1, only the conversion to lower case is done with up to 32 characters. This is useful for networks, where only Windows NT or Windows 95 PCs are used, but not if Windows for Workgroups clients are used. hfsiso=1 iXOS-JUKEMAN supports Apple HFS CDs and Hybrid CDs which contain both HFS and ISO 9600 directory structures.
Server parameters It is often preferable to delay this disk exchange as data requests are usually queued for the current disk. This parameter sets a limit according the delay. Value 0 means a strict serial use of the access queue (not very sensible). The greater the value the longer the delay even if there is not access to the disk. rahead=3 Specifies the number of chunks the data cache tries to read ahead. reject=1 Specifies how incomplete disks are treated (e. g.
Using iXOS-JUKEMAN Name Unit Default value Minimum Maximum autodc 1 0 2 blanks 0 0 2 fullvn 0 0 1 ignore 0 0 1 60 0 3,600 loglev 4 0 9 lwords 5 0 9 mdelay 3 0 99 rahead 3 0 1000 60 0 99,999,999 iotimo trayto seconds seconds Static parameters cdnfsp=100003 This parameter defines with which program number iXOS-JUKEMAN registers its NFS service, if no other program of that kind exists. Value 0 means no registration.
Server parameters Specifies how many processes can be started. mountp=20000234 Defines the program number the server uses to register its mount service if there is no such program already registered. Use 0 for no registration at all. nonfsd=0 Set this parameter to 1 to prevent the NFS server built in iXOS-JUKEMAN from starting. This is only useful on Windows NT, as NFS is the only way to connect to the file system if iXOS-JUKEMAN is running on UNIX.
Using iXOS-JUKEMAN Name Unit Default value Minimum Maximum maxcvt 1,000 10 65,536 maxthr 40 12 1,024 mountp 20,000,234 0 99,999,999 nonfsd 0 0 1 portno 4,027 (2,049) 1 65,536 131,072 8,192 16,777,216 0 0 1 0 0 3,600 rtrack bytes synclm waitpm 128 seconds iXOS-JUKEMAN 2.2 User Manual Pre.
Using iXOS-JUKEMAN 4.11.2 Change server parameters GUI Windows NT Select [CONFIGURATION]-PARAMETERS: The dialog shows a list of server parameters along with their current values, their permanent values from the file server.cfg and the default values. Select the parameter you wish to change and click [EDIT], double-click the parameter. In the “Permanent” text field, the value in the file server.cfg can be set.
Server parameters CLI UNIX, Windows NT In server.cfg, all server parameters have the common format { }. is the name of the parameter and is a nonnegative integer in decimal or hex notation. Change parameters permanently To change a value permanently, add an entry in server.cfg. If there is no parameters section, create it and list all parameters to be changed. For example, you want to change the log level of the server which is set with the parameter loglev.
Using iXOS-JUKEMAN 4.12 Burning disks/writing incrementally It is possible to write data to disks in two ways with iXOS-JUKEMAN, namely, in batch mode or incrementally and transparently using the file system. Batch mode was also a feature of version 1.3b of iXOS-JUKEMAN. The writeable disks are placed in the jukebox and the recorder is reserved for the write process.
Burning disks/writing incrementally 4.12.1 Burning disks (Single Track at Once) The writing software in iXOS-JUKEMAN can transport the data to be written to a CD, PD, WORM or MO recorder drive. To actually burn a disk, you need the writing software cdglow together with iso9660, the latter used to generate the required standard ISO 9660 file system. Windows NT also supports the burning of disks from the GUI.
Using iXOS-JUKEMAN In addition to this, no activites or real-time processes, which would overload the hard disk or SCSI busses, should be allowed to run while burning a CD. If you are unsure about the properties of a device, the cdglow command should be run with the option -p. Though it is usually not possible to simulate the laser performance, this option allows the recording process to be simulated and whether buffer underrun error is likely to occur.
Burning disks/writing incrementally -a the granularity of the control-output, which determines the frequency with which confirmation messages are output when recording data - default value is 1 MB, which corresponds to -a 0x100000. This means that for every megabyte of data written to the CD, a message will be output. The actual value provided for will be rounded up to the nearest MB. If is set to 0, then no messages are output.
Using iXOS-JUKEMAN iso9660 iso9660 is program which formats a file system to the ISO 9660 standard. This allows the use of the Rock Ridge extensions, which contain information about UNIX file names and permissions. A file system resulting from this program can be written to its own partition or file before it is burned onto disk. Alternatively, depending on the hardware (see above), it can be channelled directly to cdglow, whereupon the need for such a large interim storage is avoided.
Burning disks/writing incrementally fitcd With this parameter it is possible to check if the size of a resultant image would be greater than the storage capacity of a 74-minute CD (650 MB). Should this be the case, the program discontinues, thus preventing an image being generated that would not actually fit onto a CD.
Using iXOS-JUKEMAN Sets the name of the medium, which is stored in the so-called “primary volume descriptor”. To avoid problems, no white space should appear in this name. publisher=“Text”, preparer=“Text”, applid=“Text” Specifies the publisher, the preparer and the application ID. ignore= This allows certain files to be excluded from the image. The program considers the original file names as though the string were removed.
Burning disks/writing incrementally Options and parameters which do not conform to ISO 9660 It must be emphasized that the use of the following options will lead to ISO 9660 images which will not be fully readable by all operating systems. longnames Permits the use of long file names. nicenames Allows any character to be used to construct the file name. However, it is better to use the option allow= (see below). noversion Suppresses the version number. dir.ext Permits the use of '.
Using iXOS-JUKEMAN Examples Consider a CD recorder which is connected to the first SCSI bus with the ID 6. It will therefore be addressed by als \\.\p0b0t6 or /dev/iXOS_SCSI0/6. These values can be checked out with the command inquiry as follows: inquiry \\.\p0b0t6 or inquiry /dev/iXOS_SCSI0/6 This provides you with the manufacturer and the product number. As soon as you have identified the Cd recorder, you can burn a Cd with the follwing: iso9660 source=\ixos | cdglow -t \\.
Burning disks/writing incrementally or. iso9660 rr name=USR1 source=/usr1 > /tmp/image This example generates an ISO 9660 image from the directory tree \usr1 (or /usr1) with Rock Ridge extensions. CD can also be copied, if you have a second drive, e.g., \\.\p0b0t3 or. /dev/iXOS_SCSI0/3: cdglow -v -s \\.\p0b0t3 -t \\.\p0b0t6 or. cdglow -v -s /dev/iXOS_SCSI0/3 -t /dev/iXOS_SCSI0/6 These commands copy one Cd to another and verify the results.
Using iXOS-JUKEMAN versions. Likewise, the CD-Rs you intend to write can be included in the set of slots administered by iXOS-JUKEMAN. First you disable the recorder drive of your jukebox for use by the file system with the command cdadm detach jb.dev -d 4 (see also “Command line index” on page213). This assumes that the jukebox description file is jb.dev and that the recorder is the fourth drive of the jukebox. After burning the disk the drive can be reattached with the command cdadm attach jb.
Burning disks/writing incrementally This has the effect of moving a CD from slot 9 to the recorder drive (4) of the jukebox (jb.dev). The CD can now be recorded like in any other CD recorder, while still allowing other CDs to be read. An example the required command is: cdglow -v -s C:\temp\image.iso -S -t \\.\p1b0t5 or. cdglow -v -s /tmp/image.iso -S -t /dev/iXOS_SCSI1/5 This command burns the ISO image onto the CD found attached to SCSIID 5 of the second SCSI controller and carries out a verification.
Using iXOS-JUKEMAN burned. This value is either the SCSI-ID of another drive or the name of the file where the ISO file system image can be found. Finally, indicates the a list of all the slots containing the CDs to be burned. Assuming jukebox.dev, is the device description file, C:\temp\source.iso or /tmp/source.iso the file containing the ISO file system image, \\.
Burning disks/writing incrementally tor that everything was successful is when the files correspond to each slot are the same size or if they differ only by a one or two bytes. Configuring burncds.sh (.bat) and makecd.bat The above scripts must be tailored to the system configuration before being used. The specific lines which may need to be changed are indicated by the trailing comment # CONFIGURE or by the leading/trailing comments rem CONFIGURE BEGIN and rem CONFIGURE END gesetzt. Such lines in burncds.
Using iXOS-JUKEMAN If the recorder drive is not the fist jukebox drive (i.e. the first drive listed in the device description file), then the parameter 1 must be replaced by the actual recorder drive number. %jukeroot%\cdglow -v -b 0x400000 %glowoption% -s %jukesource% -t %jukedest% This line initiates the actual recording process Further options for cdglow may also be added in here, e.g.
Burning disks/writing incrementally GUI Windows NT Select [WRITE]-SINGLE TRACK AT ONCE. The following dialogue box appears: Source: You can select one of the following sources: ISO-Image Choose from the selection the appropriate ISO disk image. Disc Drive Select the appropriate source drive from the list. Jukebox Select the jukebox, the source drive and the required slots. iXOS-JUKEMAN 2.2 User Manual Pre.
Using iXOS-JUKEMAN FS Tree Select a directory using FS Tree. There are a variety of sources for this option: Volume label indicates what the newly-recorded disk should be called. The ISO Options are described in sections “ISO 9660-conforming parameters and options” on page 136 and the Non ISO Options in section “Options and parameters which do not conform to ISO 9660” on page 139. [COMPUTE VOLUME SIZE] can be used to find out the size of the disk to be recorded. 148 iXOS-JUKEMAN 2.2 User Manual Pre.
Burning disks/writing incrementally [EDIT TREE] is used to exclude, insert or rename specific files or subdirectories.: [DELETE]: Deletes the selected file or sub-directory from the tree. The file or directory will then be marked with a red cross and be excluded from the recording. [INSERT]: Allows a file or sub-directory to be inserted into the tree at a preselected point.
Using iXOS-JUKEMAN Target: You can choose one of the following targets: ISO-Image Select the target directory from the list provided and type in the name for the ISO image. Recorder Choose the recorder drive from the list. You can set the speed of the recording here (single-, dual- or maximaum speed). The option write in test mode only allows a simulation to be car- 150 iXOS-JUKEMAN 2.2 User Manual Pre.
Burning disks/writing incrementally ried out. Both burn data to the disc and burn data and verify it can be used to start the recording process, in the latter case also with a verification flag. Jukebox Choose the jukebox, recorder drive and required slots. From iXOSJUKEMAN 2.2 and later versions, it is possible to select more than one slot, so that several CD can be burned using the same source. The individual slots can be selected by using the [CTRL] key or, if the slots are consecutive, using [SHIFT].
Using iXOS-JUKEMAN will be written in accordance with Level 1 of the ISO 9660 file system standard. Of particular relevance is that the file names will then have conform to the 8.3 standard will original file names will be converted accordingly. If you do not have a valid license (c.f. “Set up license keys” on page 31) for cdglow, which is normally stored in writer.lic, it is possible to write up to a maximum of 128 MB to a disk.
Burning disks/writing incrementally +S Size of disk including free space +B Size of buffered data +W Size of written data +w W+B (data size for a disk) +F S-W (free physical space for a disk) +f S-w (free space for further data) +T number of written tracks All results in kB (1024 Byte) The following is a detailed description of the commands: cdadm writer action=format location= Format the specified disk (not possible for CD-Rs, but for MOs, and PDs as well as hard disk images).
Using iXOS-JUKEMAN Example: cdadm writer fsi=ifs action=init location=jukebox.dev,1 vname=CDR_001 The incremental file system can be tested with hard disk images, even If you do not have a recorder or writeable disks (see “Disk images on hard disk” on page 209). This can be set-up using the GUI on NT or by creating a device description file (e. g., iso.dev), with the following contents: Windows NT device=image drive=C:\temp\rfs.iso UNIX device=image drive=/tmp/rfs.iso The file C:\temp\rfs.
Using iXOS-JUKEMAN 4.12.3 How to write disks incrementally GUI Windows NT Select [CONTENTS]: Select [INCREMENTAL FS...]: At least one separate recorder or a recorder in a jukebox enabled for IFS is needed to use the incremental file system. Alternatively, to test the functionality a hard disk image can be used (see “Disk images on hard disk” on page 209). Format disk 156 iXOS-JUKEMAN 2.2 User Manual Pre.
Burning disks/writing incrementally Click [FORMAT]. Formatting of a disk may take some time. Initialize disk The disk needs to be initialized before files can be actually written to it. Writeable disks appear as -badCD- or -blank- in the list, deppending of the recorder. Select the disk to be initialized and click [INITIALIZE...]. You will be asked for the disk label, and the disk is initialized using this name. Once the disk is initialized files can be copied to it.
Using iXOS-JUKEMAN CLI UNIX, Windows NT Initialize disk cdadm writer fsi=ifs action=init location=jb.dev,27 vname=vol This command initializes the CD-R in slot 27 of device jb.dev using the name “vol”. Once the disk is initialized files can be copied to it. Everything written to the disk is stored in the IFS buffer first. Write buffered data To actually write the buffered data to the disk issue the command: cdadm writer action=flush vname=vol This will write an additional track to the disk.
Burning disks/writing incrementally Test disk To make the finalized disk visible in the file system, issue the following command: cdadm testcd jb.dev 27 This instructs iXOS-JUKEMAN, to test the CD in slot 27 and add it to the file system. iXOS-JUKEMAN 2.2 User Manual Pre.
Using iXOS-JUKEMAN 4.12.4 WORM file system Note: The WORM file system is for system integrators. End users should configure and use it with special care. The WORM file system is a special file system implementation to write WORMs, MOs, and PDs (but not CD-Rs) incrementally and more efiiciently. Compared to the IFS, files are written directly to the disks so there is not need to issue a cdadm writer flush command.
Burning disks/writing incrementally } ixwinodes { nodesize { 64 } files { file1 file2 } file1 { path { e:\testdata\inode1 } size { 200 } mode { file } } file2 { path { e:\testdata\inode2 } size { 200 } mode { file } } } } Parameter maxOpenDatafiles Meaning numInodes Total number of files/directories that can be managed by the hash tables of the WORM file systems. Limit for the number of rehashes, which must be exceeded to issue warnings (“file system is getting full”).
Using iXOS-JUKEMAN Using the WORM file system If you entered the section ixworm in the file server.cfg a disk can be initialized after the next server start-up using the following command: cdadm writer fsi=ixw action=init location= [size=] [blksize=] vname= fsi=ixw selects the WORM file system. is in the format ,. is the name of the device description file, is the slot number.
Introduction 5 Supported jukeboxes 5.1 Introduction The hardware can be chosen from a variety of jukeboxes for CD-ROMS and writable disks. It does not matter that most of these devices are controlled in different ways. Most functional differences are invisible for the user, but some properties have an impact on the user interface. For instance, a jukebox lacking a mail slot usually will not change disks itself upon request.
Supported jukeboxes 5.2 ASM CDR???? Device type: standard Windows NT device=standard drive=\\.\p0b0t3 drive=\\.\p0b0t4 drive=\\.\p0b0t5 drive=\\.\p0b0t6 robot=\\.\p0b0t1 save=*.sav UNIX device=standard drive=/dev/iXOS_SCSI0/3 drive=/dev/iXOS_SCSI0/4 drive=/dev/iXOS_SCSI0/5 drive=/dev/iXOS_SCSI0/6 robot=/dev/iXOS_SCSI0/1 save=*.sav ASM provides a range of CDR jukeboxes with capacities from 100-1563 CDs. Up to 44 CD-ROM or CD-R drives can be fitted. Only drives with caddies are supported.
Cope CD Tower 5.3 Cope CD Tower Device type: tower Windows NT device=tower drive=\\.\p0b0t1,0 UNIX device=tower drive=/dev/iXOS_SCSI0/4,0 The SCSI IDs of the Cope Tower are mapped to LUNs internally. This means you can connect up to seven towers with up to 49 drives to a single SCSI bus. You need to enter only one drive in the device description file, the rest is done by iXOS-JUKEMAN. You do not need to provide a save file as it has no effect.
Supported jukeboxes 5.4 Cygnet Infinidisc/Infiniwriter Device type: cygnet Windows NT device=cygnet drive=\\.\p0b0t4 drive=\\.\p0b0t5 robot=\\.\p0b0t1 save=*.sav UNIX device=cygnet drive=/dev/iXOS_SCSI0/4 drive=/dev/iXOS_SCSI0/5 robot=/dev/iXOS_SCSI0/1 save=*.sav The Cygnet Infinidisc is a modular jukebox for CDs/CD-Rs. It supports 250 CDs (expandable to 500 CDs using a second Disk Storage Unit DSU). The number of drives can be 2 up to 8 for an Infinidisc 250 (with DSU), or 4 for an Infinidisc 500.
Cygnet ID100 5.5 Cygnet ID100 Device type: cygnet_id100 Windows NT device=cygnet_id100 drive=\\.\p0b0t3 drive=\\.\p0b0t4 drive=\\.\p0b0t5 robot=\\.\p0b0t1 save=*.sav UNIX device=cygnet_id100 drive=/dev/iXOS_SCSI0/3 drive=/dev/iXOS_SCSI0/4 drive=/dev/iXOS_SCSI0/5 robot=/dev/iXOS_SCSI0/1 save=*.sav The ID100 can be equipped with up to 5 packs containing 20 CDs each. Up to 4 drives can be fitted in the jukebox. The robot is addressed through SCSI-2.
Supported jukeboxes 5.6 Denon DRD-1408 Device type: denon200 Windows NT device=denon200 drive=\\.\p2b0t4 drive=\\.\p2b0t5 robot=\\.\p2b0t6 save=*.sav UNIX device=denon200 drive=/dev/iXOS_SCSI2/4 drive=/dev/iXOS_SCSI2/5 robot=/dev/iXOS_SCSI2/6 save=*.sav The Denon DRD-1408 jukebox for 200 CDs is equipped with two 8-speed reader drives. Disk changes are performed similar to the NSM CDR 100 by removing the packs, inserting the disks into the packs, and reinserting the packs again.
DISC 5.7 DISC Device type: disc Windows NT device=disc drive=\\.\p0b0t2 drive=\\.\p0b0t3 drive=\\.\p0b0t4 drive=\\.\p0b0t5 robot=\\.\p0b0t6 save=*.sav UNIX device=disc drive=/dev/iXOS_SCSI0/2 drive=/dev/iXOS_SCSI0/3 drive=/dev/iXOS_SCSI0/4 drive=/dev/iXOS_SCSI0/5 robot=/dev/iXOS_SCSI0/6 save=*.sav DISC offers a wide range of jukeboxes with capacities that range from 250 to 1,500 CDs. The number of drives and recorders varies between 18 and 28.
Supported jukeboxes 5.8 DISC DA***.* Device type: disc_da Windows NT device=disc_da drive=\\.\p0b0t3,0 robot=\\.\p0b0t3,1 save=*.sav UNIX device=disc_da drive=/dev/iXOS_SCSI0/3,0 robot=/dev/iXOS_SCSI0/3,1 save=*.sav These jukeboxes are equipped with up to 4 drives (reader or recorder drives supported by iXOS-JUKEMAN). The DISC DA jukeboxes have a mail slot just like the NSM Mercury or the Pioneer DRM 1004X. The DISC DA is controlled through SCSI and achieves good CD change and access times.
DISC CD-CHG DJ-200/600 5.9 DISC CD-CHG DJ-200/600 Device type: disc_dj Windows NT device=disc_da drive=\\.\p0b0t3,0 robot=\\.\p0b0t3,1 save=*.sav UNIX device=disc_da drive=/dev/iXOS_SCSI0/3,0 robot=/dev/iXOS_SCSI0/3,1 save=*.sav The DISC CD-CHG jukeboxes contain 200 or 600 CDs and can be equipped with 2 to 6 drives (4 reader and 2 recorder drives). The robot is controlled through SCSI-2. The jukeboxes have a mail slot. The CDs are placed in packs of 50 CDs.
Supported jukeboxes 5.10 DSM Terastore Jukeboxen Device type: dsm Windows NT device=dsm drive=\\.\p0b0t3,0 robot=\\.\p0b0t3,1 save=*.sav UNIX device=dsm drive=/dev/iXOS_SCSI0/3,0 robot=/dev/iXOS_SCSI0/3,1 save=*.sav DSM offers jukeboxes starting from 28 up to 1,600 disks (CDs, WORMs or MOs). The number of drives is highly configurable. The disk change is performed by means of an exchange slot. Please make sure to insert the caddies into the exchange slot so the arrow points to you, not to the jukebox.
ELMS DVL 5.11 ELMS DVL Device type: elms Windows NT device=elms drive=\\.\p0b0t3 drive=\\.\p0b0t4 drive=\\.\p0b0t5 drive=\\.\p0b0t6 robot=\\.\p0b0t1 save=*.sav UNIX device=elms drive=/dev/iXOS_SCSI0/3 drive=/dev/iXOS_SCSI0/4 drive=/dev/iXOS_SCSI0/5 drive=/dev/iXOS_SCSI0/6 robot=/dev/iXOS_SCSI0/1 save=*.sav The DVL can contain up to 5 packs, with 20 CDs each. Up to 4 drives can be fitted in the jukebox. The robot is controlled through SCSI-2.
Supported jukeboxes 5.12 Grundig GMS 1035 Device type: grundig35 Windows NT device=grundig35 drive=\\.\p0b0t3 drive=\\.\p0b0t4 robot=\\.\p0b0t5 save=*.sav UNIX device=grundig35 drive=/dev/iXOS_SCSI0/3 drive=/dev/iXOS_SCSI0/4 robot=/dev/iXOS_SCSI0/5 save=*.sav The Grundig GMS 1035 has room for 35 CDs and 2 drives, on of which can be a recorder drive. The device type is 'grundig35'. The jukebox may have a mail slot, which is, however, hidden by a door, which you should not open during normal operation.
Grundig GMS 3200 5.13 Grundig GMS 3200 Device type: grundig200 Windows NT device=grundig200 drive=\\.\p1b0t3 drive=\\.\p1b0t4 drive=\\.\p1b0t5 drive=\\.\p1b0t6 robot=\\.\p1b0t2 save=*.sav UNIX device=grundig200 drive=/dev/iXOS_SCSI1/3 drive=/dev/iXOS_SCSI1/4 drive=/dev/iXOS_SCSI1/5 drive=/dev/iXOS_SCSI1/6 robot=/dev/iXOS_SCSI1/2 save=*.sav The Grundig jukebox GMS 3200 can take up to 200 CDs, and has four reader or recorder drives. It has a mail slot like the Mercury and a SCSI robot.
Supported jukeboxes 5.14 Grundig GMS 3280 Device type: grundig280 Windows NT device=grundig280 drive=\\.\p1b0t1 drive=\\.\p1b0t2 drive=\\.\p1b0t3 drive=\\.\p1b0t4 drive=\\.\p1b0t5 drive=\\.\p1b0t6 robot=\\.\p1b0t0 save=*.sav UNIX device=grundig280 drive=/dev/iXOS_SCSI1/1 drive=/dev/iXOS_SCSI1/2 drive=/dev/iXOS_SCSI1/3 drive=/dev/iXOS_SCSI1/4 drive=/dev/iXOS_SCSI1/5 drive=/dev/iXOS_SCSI1/6 robot=/dev/iXOS_SCSI1/0 save=*.sav The Grundig jukebox GMS 3280 contains 8 packs with 35 CDs each.
HP WORM/MO 5.15 HP WORM/MO Device type: worm Windows NT device=worm drive=\\.\p0b0t1 drive=\\.\p0b0t2 drive=\\.\p0b0t3 robot=\\.\p0b0t4 save=*.sav UNIX device=worm drive=/dev/iXOS_SCSI0/1 drive=/dev/iXOS_SCSI0/2 drive=/dev/iXOS_SCSI0/3 robot=/dev/iXOS_SCSI0/4 save=*.sav The HP WORM/MO jukeboxes are available in all different configurations with up to 12 drives and 238 disks. The robot is controlled through SCSI2. iXOS-JUKEMAN 2.2 User Manual Pre.
Supported jukeboxes 5.16 Hyundai HAS-550 Device type: hyundai Windows NT device=hyundai drive=\\.\p0b0t1 robot=\\.\p0b0t4 save=*.sav UNIX device=hyundai drive=/dev/iXOS_SCSI0/1 robot=/dev/iXOS_SCSI0/4 save=*.sav The Hyundai HAS-550 has the device type hyundai and a mail slot. This jukebox has an interesting design where the drive at the same time works as a transporter. 178 iXOS-JUKEMAN 2.2 User Manual Pre.
JVC MC-* CDROM Library 5.17 JVC MC-* CDROM Library Device type: jvc Windows NT device=jvc drive=\\.\p0b0t0 drive=\\.\p0b0t1 drive=\\.\p0b0t2 robot=\\.\p0b0t4 save=*.sav UNIX device=jvc drive=/dev/iXOS_SCSI0/0 drive=/dev/iXOS_SCSI0/1 drive=/dev/iXOS_SCSI0/2 robot=/dev/iXOS_SCSI0/4 save=*.sav The JVC jukeboxes contain 200 or 600 CDs and can be fitted with 2 to 6 drives (4 reader and 2 recorder drives). The robot is controlled through SCSI-2. CDs can be changed conveniently with the mail slot.
Supported jukeboxes 5.18 Kodak 100/150 CD ADL 100/150 Device type: cdr100 bzw. mercury When used with iXOS-JUKEMAN the Kodak jukeboxes are identical to the NSM CDR 100 (ADL 100) or NSM Mercury (ADL 150). 180 iXOS-JUKEMAN 2.2 User Manual Pre.
Kodak CDL 144 5.19 Kodak CDL 144 Device type: kodak_cdl Windows NT device=kodak_cdl drive=\\.\p0b0t3 robot=\\.\p0b0t4 save=*.sav UNIX device=kodak_cdl drive=/dev/iXOS_SCSI0/3 robot=/dev/iXOS_SCSI0/4 save=*.sav The CD Library 144 jukebox can be fitted with 1 to 4 CD-ROM/CD-R drives. The drives and packs of 18 CDs allow a flexible use of the jukebox. Between 108 and 162 CDs can be loaded. The doors can be locked and a mail slot secured by a password keeps your data safe.
Supported jukeboxes 5.20 Kubik 240 CD Jukebox Device type: kubik Windows NT device=kubik drive=\\.\p0b0t3 drive=\\.\p0b0t4 drive=\\.\p0b0t5 drive=\\.\p0b0t6 robot=com1: save=*.sav UNIX device=kubik drive=/dev/iXOS_SCSI0/3 drive=/dev/iXOS_SCSI0/4 drive=/dev/iXOS_SCSI0/5 drive=/dev/iXOS_SCSI0/6 robot=/dev/tty0 save=*.sav In Kubik’s CDR240M 240 CDs are arranged in a flat roundabout.
MDI CD 150 5.21 MDI CD 150 Device type: mercury As related to iXOS-JUKEMAN, this jukebox is identical to the NSM Mercury. iXOS-JUKEMAN 2.2 User Manual Pre.
Supported jukeboxes 5.22 Nakamichi 7 CD MCD-1020 Device type: nakamichi or nec Windows NT device=nakamichi drive=\\.\p0b0t2,0 save=nec.sav UNIX device=nakamichi drive=/dev/iXOS_SCSI0/2,0 save=nec.sav The small Nakamichi changer is a good choice for evaluating iXOSJUKEMAN in demo mode. Up to 7 disks can be inserted into this changer. 184 iXOS-JUKEMAN 2.2 User Manual Pre.
Nakamichi 4 CD MJ-4.8s 5.23 Nakamichi 4 CD MJ-4.8s Device type: nakamichi oder nec device=nec drive=\\.\p0b0t4,0 save=*.sav device=nec drive=/dev/iXOS_SCSI0/4,0 save=*.sav This 4 CD changer with an 8x drive, suitable as an internal device, is very well suited as a fast device in a hierarchical jukebox system. iXOS-JUKEMAN 2.2 User Manual Pre.
Supported jukeboxes 5.24 Nakamichi MJ-5.16si Device type: nakamichi Windows NT device=nakamichi drive=\\.\p0b0t3,0 save=*.sav UNIX device=nakamichi drive=/dev/iXOS_SCSI0/3,0 save=*.sav The Nakamichi MJ-5.16si is a 5 CD changer with a 16x drive. 186 iXOS-JUKEMAN 2.2 User Manual Pre.
NSM 100 CD Jukebox 5.25 NSM 100 CD Jukebox Device type: cdr100 Windows NT device=cdr100 drive=\\.\p0b0t4 robot=com1: robid=4 save=cdr100.sav UNIX device=cdr100 drive=/dev/iXOS_SCSI0/4 robot=/dev/ttya robid=4 save=cdr100.sav The CDR100 offers a capacity of 100 CDs and a high performance due to its small size. The devices are controlled efficiently by serial lines using a special protocol which allows up to 16 devices to be daisy-chained.
Supported jukeboxes door and change disks without impacting the clients. Clients do not receive errors, but they must wait for a response. As soon as you finish changing the CDs, close the door and tell the server which CDs you changed and to resume to normal operation.
NSM 150 CD Mercury 20/31/40 5.26 NSM 150 CD Mercury 20/31/40 Device type: mercury Windows NT device=mercury drive=\\.\p0b0t3 drive=\\.\p0b0t4 drive=\\.\p0b0t5 drive=\\.\p0b0t6 robot=com2:,0 save=mercury.sav UNIX device=mercury drive=/dev/iXOS_SCSI0/3 drive=/dev/iXOS_SCSI0/4 drive=/dev/iXOS_SCSI0/5 drive=/dev/iXOS_SCSI0/6 robot=/dev/ttyb,0 save=mercury.sav iXOS-JUKEMAN fully uses the Mercury’s parallel capabilities and effectively servers 14 requests per minute for different CDs with a single Mercury.
Supported jukeboxes and the jukebox opens the tray. Insert a CD and press any button or the tray, and the jukebox closes the tray. The server inspects the new CD and it appears in the server’s file system views. If you want to remove a CD, call: cdadm remove and the server moves a CD to the tray and opens it. The server preferably removes an invalid CD. If you want to choose a particular CD, you can specify its slot number or name in the default name format.
NSM 150 CD Mercury 20s/31s/40s 5.27 NSM 150 CD Mercury 20s/31s/40s Device type: standard Windows NT device=standard drive=\\.\p0b0t2 drive=\\.\p0b0t3 drive=\\.\p0b0t4 drive=\\.\p0b0t5 robot=\\.\p0b0t6 save=mercury.sav UNIX device=standard drive=/dev/iXOS_SCSI0/2 drive=/dev/iXOS_SCSI0/3 drive=/dev/iXOS_SCSI0/4 drive=/dev/iXOS_SCSI0/5 robot=/dev/iXOS_SCSI0/6 save=mercury.sav These jukeboxes differ from the respective models without the trailing ‘s’ by using SCSI control instead of a serial line.
Supported jukeboxes 5.28 NSM Satellite (serial) Device type: satellite Windows NT device=satellite drive=\\.\p0b0t3 drive=\\.\p0b0t4 drive=\\.\p0b0t5 drive=\\.\p0b0t6 robot=com2:,0 save=*.sav UNIX device=satellite drive=/dev/iXOS_SCSI0/3 drive=/dev/iXOS_SCSI0/4 drive=/dev/iXOS_SCSI0/5 drive=/dev/iXOS_SCSI0/6 robot=ttyb,0 save=*.sav The NSM Satellite combines the reliability of NSM jukeboxes with a modular design. The Satellite has a capacity of 60 to 135 CDs and can be fitted with up to four drives.
Panasonic LF-J50/100/200 CD Jukebox 5.29 Panasonic LF-J50/100/200 CD Jukebox Device type: ps_lf_j Windows NT device=ps_lf_j drive=\\.\p0b0t4 drive=\\.\p0b0t3 drive=\\.\p0b0t2 robot=\\.\p0b0t6 save=ps.sav UNIX device=ps_lf_j drive=/dev/iXOS_SCSI0/4 drive=/dev/iXOS_SCSI0/3 drive=/dev/iXOS_SCSI0/2 robot=/dev/iXOS_SCSI0/6 save=ps.sav iXOS-JUKEMAN supports the Panasonic LF-J* jukeboxes with with double-head drives for CD-ROMs and 'Phase change' disks.
Supported jukeboxes 5.30 Pioneer 6 CD Changer Device type: pioneer6 Windows NT device=pioneer6 drive=\\.\p0b0t3 save=*.sav UNIX device=pioneer6 drive=/dev/iXOS_SCSI0/3 save=*.sav The Pioneer 6-pack has several variations, depending on the type of drive used. DRM-602x, DRM-604x, and DRM-624x mainly differ in speed. The changer is always invisible, and it has no separate address, so the device description file does not specify a robot.
Pioneer 18 CD Changer 5.31 Pioneer 18 CD Changer Device type: pioneer18 Windows NT device=pioneer18 drive=\\.\p0b0t3,0 robot=\\.\p0b0t3,1 save=*.sav UNIX device=pioneer18 drive=/dev/iXOS_SCSI0/3,0 robot=/dev/iXOS_SCSI0/3,1 save=*.sav The DRM-1804x 18-CD changer uses three small 6-pack magazines. It addresses the actual changer separately, so it must be specified in the device description file. The changer is always LUN 1 of the drive.
Supported jukeboxes 5.32 Pioneer 100 CD Jukebox Device type: pioneer100 Windows NT device=pioneer100 drive=\\.\p0b0t4 drive=\\.\p0b0t3 drive=\\.\p0b0t2 robot=\\.\p0b0t6 save=p100.sav UNIX device=pioneer100 drive=/dev/iXOS_SCSI0/4 drive=/dev/iXOS_SCSI0/3 drive=/dev/iXOS_SCSI0/2 robot=/dev/iXOS_SCSI0/0 save=p100.sav This jukebox contains up to 100 CDs and two to four drives.
Pioneer 500 CD Jukebox 5.33 Pioneer 500 CD Jukebox Device type: pioneer500 Windows NT device=pioneer500 drive=\\.\p0b0t2 drive=\\.\p0b0t3 drive=\\.\p0b0t4 drive=\\.\p0b0t5 robot=\\.\p0b0t6 save=*.sav UNIX device=pioneer500 drive=/dev/iXOS_SCSI0/2 drive=/dev/iXOS_SCSI0/3 drive=/dev/iXOS_SCSI0/4 drive=/dev/iXOS_SCSI0/5 robot=/dev/iXOS_SCSI0/6 save=*.sav The Pioneer DRM-5004x offers 4 drives and room for 500 CDs. Both the robot and the drives are controlled by SCSI.
Supported jukeboxes a CD is exported with the changer. Open the door as soon as the command returns, remove the CD, and close the door to resume normal operation. You can also specify a slot number or CD name: cdadm -f remove device x11r5 instructs the server to remove the CD named x11r5. The DRM-5004x can be fitted with recorders supported by iXOSJUKEMAN. 198 iXOS-JUKEMAN 2.2 User Manual Pre.
Plasmon D-Series 5.34 Plasmon D-Series Device type: plasmond Windows NT device=plasmond drive=\\.\p0b0t2 drive=\\.\p0b0t3 robot=\\.\p0b0t1 save=*.sav UNIX device=plasmond drive=/dev/iXOS_SCSI0/2 drive=/dev/iXOS_SCSI0/3 robot=/dev/iXOS_SCSI0/1 save=*.sav The Plasmon D-Series is available with room for 120, 240, or 480 slots for CDs or PDs, and can have 2, 4, or 6 drives fitted. PDs cannot be changed using the mail slot.
Supported jukeboxes 5.35 Plasmon 150 CD-Jukebox Device type: standard Windows NT device=standard drive=\\.\p0b0t2 drive=\\.\p0b0t3 drive=\\.\p0b0t4 drive=\\.\p0b0t5 robot=\\.\p0b0t6 save=*.sav UNIX device=standard drive=/dev/iXOS_SCSI0/2 drive=/dev/iXOS_SCSI0/3 drive=/dev/iXOS_SCSI0/4 drive=/dev/iXOS_SCSI0/5 robot=/dev/iXOS_SCSI0/6 save=*.sav As related to iXOS-JUKEMAN the Plasmon CD150J is identical to the NSM Mercury 40s/31s range of jukeboxes.
Plextor Megaplex oder PX-J2200 200 CD Jukebox 5.36 Plextor Megaplex oder PX-J2200 200 CD Jukebox Device type: plextor200 Windows NT device=plextor200 drive=\\.\p2b0t4 drive=\\.\p2b0t5 robot=\\.\p2b0t6 save=plextor.sav UNIX device=plextor200 drive=/dev/iXOS_SCSI2/4 drive=/dev/iXOS_SCSI2/5 robot=/dev/iXOS_SCSI2/6 save=plextor.sav The Plextor Jukebox provides space for 200 CDs and is fitted with 2 reader drives. CD changes are performed similar to the NSM CDR 100. iXOS-JUKEMAN 2.2 User Manual Pre.
Supported jukeboxes 5.37 Smart and Friendly 7 CD CDJ 7004 Device type: nakamichi oder nec As related to iXOS-JUKEMAN this changer is identical to the Nakamichi MCD-1020. 202 iXOS-JUKEMAN 2.2 User Manual Pre.
Smart and Friendly 4 CD CDJ 4008 5.38 Smart and Friendly 4 CD CDJ 4008 Device type: nakamichi oder nec As related to iXOS-JUKEMAN this changer is identical to the Nakamichi MJ-4.8s. iXOS-JUKEMAN 2.2 User Manual Pre.
Supported jukeboxes 5.39 Sony CDZ-R360 CD Jukebox Device type: sony_cdz Windows NT device=sony_cdz drive=\\.\p0b0t4,0 drive=\\.\p0b0t4,1 robot=\\.\p0b0t4,7 save=*.sav UNIX device=sony_cdz drive=/dev/iXOS_SCSI0/4,0 drive=/dev/iXOS_SCSI0/4,1 robot=/dev/iXOS_SCSI0/4,7 save=*.sav The Sony CDZ-R360 maintains 360 CDs in a small jukebox with 2 drives. The changer and drives use different LUNs of the same SCSI-ID, so you can connect several jukeboxes to a single bus.
Sony-CDL-2?00-?? CD Jukeboxen 5.40 Sony-CDL-2?00-?? CD Jukeboxen Device type: sony_cdl Windows NT device=sony_cdl drive=\\.\p0b0t2 drive=\\.\p0b0t3 drive=\\.\p0b0t4 drive=\\.\p0b0t5 robot=\\.\p0b0t6 save=sony_cdl.sav UNIX device=sony_cdl drive=/dev/iXOS_SCSI0/2 drive=/dev/iXOS_SCSI0/3 drive=/dev/iXOS_SCSI0/4 drive=/dev/iXOS_SCSI0/5 robot=/dev/iXOS_SCSI0/6 save=sony_cdl.sav The Sony-CDL-2100 jukeboxes provide room for 125, the CDL-2200 models for 225 CDs.
Supported jukeboxes 5.41 Standard-SCSI-2 jukeboxes Device type: standard iXOS-JUKEMAN supports all standard SCSI-2 jukeboxes with a mail slot. The device description files are similar to the Plasmon jukebox (see page 200), but may vary in the number of drives. Most standard SCSI-2 jukeboxes can be fitted with recorders supported by iXOS-JUKEMAN (see “Supported hardware” on page 16). 206 iXOS-JUKEMAN 2.2 User Manual Pre.
Tower jukeboxes with no LUN support 5.42 Tower jukeboxes with no LUN support Device type: single Windows NT device=single drive=\\.\p1b0t0 drive=\\.\p1b0t1 drive=\\.\p1b0t2 drive=\\.\p1b0t3 drive=\\.\p1b0t4 drive=\\.\p1b0t5 drive=\\.
Supported jukeboxes 5.43 Single drives Device type: single Windows NT device=single drive=\\.\p0b0t4 UNIX device=single drive=dev/iXOS_SCSI0/4 iXOS-JUKEMAN supports single drives. They are treated as small and simple jukeboxes. Several single drives can be listed in one device description file. CD changes can be performed manually without interacting with the server. The server will check these drives for disk changes periodically (see server parameter dcheck in “Server parameters” on page 123).
Disk images on hard disk 5.44 Disk images on hard disk Device type: image Windows NT device=image drive=D:\fakedisk.iso UNIX device=image drive=/fakedisk.iso Instead of real CD drives you can also use ISO 9660 formatted hard disk images of CDs (see also "iso9660" on page 136). If the file D:\fakedisk.iso or /fakedisk.iso is an ISO 9660 formatted disk image, it can be accessed with the above device description file.
Supported jukeboxes or a whole directory tree transparently. To do this, create a directory such as \images on an NTFS partition, and compress it with the file manager. All images created in this directory will be compressed automatically. Another way to create ISO 9660 files is to use the formatting program iso9660. See “iso9660” on page 136. Thus, hard disk images and transparent compression can be used to set up cost-effective and fast CD servers.
Other jukeboxes 5.45 Other jukeboxes iXOS is continually adding new features and support for new jukebox types. Send mail to support@europe.jukeman.com to get an updated list of supported devices. iXOS-JUKEMAN 2.2 User Manual Pre.
Command line index 6 Command line index 6.1 Introduction The following pages contain brief descriptions of the commands that can be passed to the program cdadm. Note: For reasons of clarity the optional paramter “-h ” is left out on the following pages. Using this parameter, the iXOSJUKEMAN server can be administered from any host where the administration client cdadm is installed. See section “Network administration” on page 96. If you want to...
Command line index If you want to... use this command: use the incremental file system cdadm writer 182 log messages cdadm logmsg 222 214 page iXOS-JUKEMAN 2.2 User Manual Pre.
Command line index cdadm attach [-d ] attach Function: Attach the specified device (or drive) to the server. The effect of this command is that the device and its volumes are controlled by iXOSJUKEMAN. The device (or drive) cannot be accessed unless it is attached. The parameter represents a valid device description file in the JUKEMAN directory. These files have the extension .dev. The extension may be omitted in the command.
Command line index cdadm byebye byebye Function: Terminate the iXOS-JUKEMAN demon cdnfsd. The server will stop and accept no further requests. The server can be restarted by running cdstart.bat (under NT) or cdnfsd (under UNIX) (see “Starting iXOSJUKEMAN” on page 87). Example: cdadm byebye cdadm down (Synonym) Error messages: Error message Meaning RPC failed: cannot connect to server *error* -3 Service not running 216 iXOS-JUKEMAN 2.2 User Manual Pre.
Command line index cdadm cvtree cvtree Function: Rescan the configurable volume tree (views). This can be useful when views are changed in the server.cfg configuration file (see “Configuration file server.cfg” on page 237). The server does not need to be restarted, to reflect changes to the views configuration. Example: cdadm cvtree Error messages: - iXOS-JUKEMAN 2.2 User Manual Pre.
Command line index cdadm detach [-d ] detach Function: Detach the specified device (or drive) from the server. The device and its volumes are no longer controlled by iXOS-JUKEMAN. The device (or drive) cannot be accessed until it is attached again. The parameter represents a valid device description file in the JUKEMAN directory. These files have the extension .dev. The extension may be omitted in the command.
Command line index cdadm getpar getpar Function: Get the value of the server parameter . Refer to the section “Server parameters” on page 245 for a list of all parameters. Server parameters may be set in the configuration file server.cfg or with the cdadm setpar command. Note that some parameters cannot be changed while the server is running. See “Static parameters” on page 126.
Command line index cdadm insert [-f] [] cdadm import [-f] [] insert import Function: Insert a disk into the specified device. The parameter represents a valid device description file in the JUKEMAN directory. These files have the extension .dev. The extension may be omitted in the command. The optional parameter may be used to specify any number and selection of slots.
Command line index iXOS-JUKEMAN 2.2 User Manual Pre.
Command line index cdadm logmsg logmsg Function: Add to the file logfile.txt. The parameter is the log level of the message. The log file is described in "Log file logfile.txt" on page 249. If goes beyond the parameter loglev, the message will not be logged. Example: cdadm logmsg 5 This goes to logfile.txt Error messages: - 222 iXOS-JUKEMAN 2.2 User Manual Pre.
Command line index cdadm movecd [] movecd Function: Move a disk from to or remove a disk from . This command will especially be useful, if you want to move a certain (writable) disk into a recorder drive to burn data on it. The parameter represents a valid device description file in the JUKEMAN directory. These files have the extension .dev. The extension may be omitted in the command.
Command line index cdadm null null Function: Check if the server is active. If the server is active, there is no result. An error message will be produced if the server is not running. Example: cdadm null Error messages: Error message Meaning RPC failed: cannot connect to server *error* -3 Server not running. 224 iXOS-JUKEMAN 2.2 User Manual Pre.
Command line index cdadm rename [[-] []] rename Function: Rename a disk in the name format . There are three possible name formats (see also “Set up views” on page 67): pc rr hs PC format (8.3) Rock Ridge extensions High Sierra format If no name format is supplied, the disk name will be changed for all name formats that match the old name specified. A single disk may have a different name for each name format. The name format that is visible to the client is set in the server.
Command line index cdadm remove [-f] [] cdadm export [-f] [] remove export Function: Remove a volume from the specified device. The parameter represents a valid device description file in the JUKEMAN directory. These files have the extension .dev. The extension may be omitted in the command. The optional parameter may be used to specify any number and selection of slots.
Command line index cdadm rescan rescan Function: Reinitializes the internal memory of the jukebox, which stores information about which slot or drive contains which disk. This command is needed for some jukeboxes, if disks were changed manually. The jukebox would not know about these changes and could damage itself as it tries to move a disk in a slot which is presumed empty.
Command line index cdadm setpar setpar Function: Set the server parameter to . Refer to the section “Server parameters” on page 245 for a list of all parameters. Server parameters also may be set in the configuration file server.cfg. Note that some parameters cannot be changed while the server is running. See “Static parameters” on page 126.
Command line index cdadm survey [] [] survey Function: Print a survey based on devices, disks, or drives, depending on several parameters, which specify the columns, restrictions and sort criterion. The following options may be specified: Meaning -d Survey based on devices -v Survey based on disks -n Survey based on the volumes database -s Survey based on the slots -r Survey based on the drives Print out...
Command line index Print out...
Command line index Note: Any name may be preceeded with : to get quoted output for that parameter, where is a single character. For instance cdadm survey -d +:'d lists all attached devices, where the device names will be quoted ('dev1.dev', 'dev2.dev'...).
Command line index Error messages: Error message Meaning usage: cdadm survey -d|-v|-s +.. *error* -1 Wrong . illegal column name x *error* -1 column name x does not exist (see table) or is not allowed in conjunction with . 232 iXOS-JUKEMAN 2.2 User Manual Pre.
Command line index cdadm testcd testcd Function: Test one or more slots of an attached device for their contents. Disks inserted manually will not be seen by the server, unless their corresponding slots are tested with this command. Depending on the jukebox type a rescan needs to be accomplished beforehand (see page 227). The parameter represents a valid device description file in the JUKEMAN directory. These files have the extension .dev.
Command line index cdadm writer … writer… Function: The "cdadm writer..." commands access the incremental file system. A detailed description can be found in the section “Burning disks incrementally” on page 151. format (1)cdadm writer action=format location= Format a PD/MO disk or a hard disk image. This may take some time. init (2) cdadm writer [fsi=ifs] action=init location= vname= Initialize a writable disk.
Command line index cdadm writer action=finalize vname=CDR_01 Error messages: Error message Meaning no vname ? *error* -1 name is missing. illegal action type *error* -1 Specified action not allowed. no vname burning *error* -1 Wrong disk name or missing . bad location *error* -1 Invalid . Maybe the slot is missing.. p_wrfs(): bad init track *error* -1 Disk has not been initialized. trec_init() fails *error* -1 Disk could not be initialized.
Configuration file server.cfg 7 Configuration file server.cfg 7.1 Introduction The main configuration file for iXOS-JUKEMAN is server.cfg. It contains sections for file system views, devices, server parameters, buffer and cache sizes, and comments. The file lives in the JUKEMAN directory. If this file does not exist under UNIX, you can create an example configuration file (see “UNIX” on page 25). Each section of this file has a name. Following this name is a block of parameters in curly brackets { ... }.
Configuration file server.cfg 7.2 The structure of server.cfg This is a sample server.
Configuration file server.cfg 7.2.1 Views This section defines a tree of views (see “Set up views” on page 67). The views are enclosed in the following structure in server.cfg: [drive { }] views { list { ... } roots { { ... } { ... } ... { ... } } } The views section may be preceeded by drive { }. All the views definded in server.cfg will be available as subdirectories of this drive letter (e. g., X) under Windows NT.
Configuration file server.cfg roots { overview { [drive { }] views { list { ... } roots { { ... } ... { ... } } } } } } Another Example: drive { Z } views { list { x y } roots { x { drive { X } discs { * } label { ALLDISCS } } y { drive { Y } views { list { a_m n_z } roots { a_m { discs { [a-m]* } } n_z { discs { [n_z]* } } } } } } The example above presents all disks under x, some under y/a_m and some under /y/n_z.
Configuration file server.cfg The tracks directory contains audio data of our experimental audio file system, which is tested for Plextor drives only and is not a component of iXOS-JUKEMAN 2.2. For more information see medium\readme.txt. The volume directory contains several views on the disk data: 1. For read access in the cached directory the data cache will be used (see “The data cache” on page 40). Write access, however, will be done directly on the SCSI device or hard disk image. 2.
Configuration file server.cfg File stupid clever Meaning Allows read and write access to the disc blocks. Used and unused block will not be distinguished. The raw file system will perform a more distinct error handling for clever files. It tries to read each block separately. Upon read failure, it asks the volume’s underlying file system for unused blocks. If all unreadable blocks turn out to be unused, the raw file system succeeds and delivers zero bytes.
Configuration file server.cfg start-up behavior of the devices. Both p18 and device3 will be attached automatically when the server is started. mercury has to be attached manually. 7.2.3 Caches and buffers Caches and buffers may be configured in the following sections. All file sizes are in MBytes. See “Set up caches and buffers” on page 36 for a detailed description. IFS (incremental file system) This is a buffer that temporarily holds data copied to wirtable disks with operating system commands.
Configuration file server.cfg size Buffer size in MBytes. inodes Maximum number of files and directories that can be stored in the buffer. volumes Maximum number of disks for this buffer. bsize Optional. Specifies the buffer block size (default: 2048 Bytes). raw Optional. If the value specified for file is a partition the parameter raw { 1 } must be added to the buffer definition. For example, to set up two buffers replace the fsbuffer { }section with the following section in server.
Configuration file server.cfg Directory cache This cache stores the directory names of the disks known to iXOSJUKEMAN. See “The directory cache” on page 36 for a detailed description. Example: dircache { file { dircache } size { 40 } } The example sets up a directory cache of 40 MB. The file name of the cache is dircache. If the line “file { dircache }” is omitted, the RAM cache size will be changed. Data cache This cache stores data read from the disks controlled by iXOS-JUKEMAN.
Configuration file server.cfg Name Default Min. Max. Function autodc 1 0 2 Caching behavior blanks 0 0 2 CD type assumption/test cdnfsp 100003 0 99999999 Program ID of NFS service 0 999999 Periodic drive checking dcheck Unit 1/100 Sec. 300 fullvn 0 0 1 PC name format (8.
Configuration file server.cfg configuration file is read in by the server. Note that the comment itself must not contain a “}” . Example: comment { I'm just a comment. I will be ignored. You know at the end. That life has been short. } iXOS-JUKEMAN 2.2 User Manual Pre.
Log file logfile.txt 8 Log file logfile.txt Normally, reading the file logfile.txt should not be necessary for purposes other than personal interest in internal server affairs. Tracing errors is also a reason the file should be consulted for. If you send us error reports by fax or email, please always include the relevant parts of the log file. All messages of the server go to the log file in the JUKEMAN directory.
Log file logfile.txt The next symbol specifies the type of process that issued the command. The process symbols are: @ controls a drive. It actually reads the data requested by clients. % controls a changer. For simple jukeboxes it may also control the drive. ? accepts NFS requests and replies immediately or queues them. $ accepts internal requests to support the native file system of the NT version. # schedules the requests from ? and $ and passes them to % and @.
Log file logfile.txt SCSI READ command. The next line reports the SCSI status and sense key together with the meaning of the sense key. The next line shows the additional sense code reported by the drive and its explanation as given in the vendors SCSI manual or in the SCSI standard. If the hardware failed, this explanation should point out which part of it failed and why.
FAQ/Troubleshooting 9 FAQ/Troubleshooting 9.1 Frequently asked questions (FAQ) This is a summary of frequently asked questions about the iXOSJUKEMAN server. 9.2 iXOS-JUKEMAN Server I connected a new jukebox to my PC and new drive letters appeared. Why did this happen? At startup time, NT inspects the hardware for devices which could represent file systems. For instance a normal (internal) CD drive fits perfectly well in this scheme.
FAQ/Troubleshooting 1. If you chose to attach the corresponding device automatically on server startup (in server.cfg either by direct editing or via the GUI), then the JUKEMAN server does the necessary changes in the NT system to hide the drive letters during the next reboot.
FAQ/Troubleshooting connect another device, say a hard disk, to the claimed address, since you won't be able to use it until you remove the claim. So you should very carefully consider what your intents are, and at least leave a note and inform your friendly local system administrator, if you choose to use this option.
FAQ/Troubleshooting Why do I get weird SCSI errors, in particular data transfer overrun messages with reference to a command “[0x8 ...]” on the console of Solaris workstations? Why do I get I/O Errors when I try to read a non root directory of a CD on Solaris? Both errors are due to problems with the Solaris Volume Management daemon, vold. It is by default configured to control all CD drives, including those which are controlled by iXOS-JUKEMAN.
FAQ/Troubleshooting You can increase the client time-out by increasing the registry value HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\ SERVICES\LANMANWORKSTATION\PARAMETERS\SessTimeOut for each client. The default is 45 (seconds). 300 is reasonable for slow jukeboxes. How to restrict access to the JUKEMAN filesystem for certain hosts? The restriction of the access to the JUKEMAN filesystem can be done with an option at the export of the filesystem.
FAQ/Troubleshooting NT: Either the IP address in the result of ipconfig or the network adapter address, which can be determined by the last entry of the “Workstation active on” line of the result of 'net config workstation' The host identifier(s) appear as wells at the top of the logfile logfile.txt in lines with the format “Your key for a licence order:”. For testing purposes, temporary licenses for a reasonable number of CDs may be obtained by contacting support@usa.jukeman.com or directly from www.
FAQ/Troubleshooting license=ijklmnop NFS server plus iXOS-JUKEMAN (NT) In iXOS-JUKEMAN a NFS server is integrated. To use another NFS server for exporting filesystems on harddisk and the jukeman filesystem, some configuration has to be done, because both compete for several ressources: - port 2049 (default for NFS services) - port 111 for the portmapper - anouncement as NFS service To tell iXOS-JUKEMAN not to start the own NFS service, the file 'server.
FAQ/Troubleshooting net use y: hostname:/views/pc /port=4027 /ro JUKEMAN does not work properly. What shall I do? As a general rule, you should first check this manual and the manual of your jukebox to ensure that your setup is o.k. A good starting point for your investigations is to reboot the host jukeman runs on, while the jukebox(es) you plan to use are properly connected and powered up. At least you should restart the server. The most useful mean for troubleshooting is the log file, logfile.
FAQ/Troubleshooting inquiry /dev/iXOS_SCSI0/4,0 0000002 /dev/iXOS_SCSI0/4,0 is TOSHIBA's CD-drive "CD-ROM XM3501TA" 0000003 ProRevL 1875, Firmware 07/06/95 If you encounter a “Bad file number” error, you should check for known devices by inquiry /dev/iXOS_SCSI?/* Alternatively you may try to attach a drive in a jukebox as a single device to check if this drive is alright. The same procedure as for drives applies to SCSI changers/robots as well, except that you can't use them as single drives of course.
FAQ/Troubleshooting Note, however, that some instances of bad CD tags are due to the fact that not all jukeboxes adhere the convention that the CD is inserted label up into the slots. The testcd takes very long This is again a problem of your hardware. Some CD drives and recorders need much time to read a CD or to detect that it is empty.
FAQ/Troubleshooting 199 for customers outside of the US or Canada, or at jukesupport@belmont.ixos.com, Tel. 415-294-5800, FAX 415-294-5836. Please be prepared to supply the following information: Hardware platform, operating system and version, iXOS jukeman version (can for instance be obtained from the first line in the logfile), the contents of the logfile.txt and of server.cfg and all devices which cause problems. iXOS-JUKEMAN 2.2 User Manual Pre.
Glossar 10 Glossar API Application Programming Interface: a set of routines, protocols, and tools for building software applications. CLI Command Line Interface, a program that will accept and execute typed in commands. See also “Conventions” on page 12. Client A program that runs locally on a host and exchanges data with a server program. Gerätebeschreibungsdatei here: A file specifying the properties of a device (e. g., a jukebox) controlled by iXOS-JUKEMAN.
Glossar IFS Incremental File System. A procedure used by iXOS-JUKEMAN to write optical disks trackwise. Using the IFS files can be copied, moved, or deleted from disks in the usual way. Inode An inode is a data structure storing file properties. Each file has an inode, describing properties such as the physical position of the file on a disk. By default an inode occupies 2048 bytes.
Glossar SCSI Small Computers System Interface: SCSI is a parallel interface ANSI standard for attaching peripheral devices to computers. SCSI-ID Unique ID of a SCSI device. WORM Write Once, Read Many: Writeable optical disk that can be written once. iXOS-JUKEMAN 2.2 User Manual Pre.
Glossar 268 iXOS-JUKEMAN 2.2 User Manual Pre.
Index 11 Index [ [option] 12 < 12 A administration client (GUI) start 87 attach 215 attach at server start (devices dialog) 62 attach automatically 102, 242 attach button 98 autodc 123 Autorun-Feature 23 available as drive (views dialog) 73 B blanks 123 buffer 36, 243 IFS 44 incremental file system 243 purge 234 write to disk 234 Burning disks 132 CLI 141 byebye 216 C cache 36, 243 for data 40, 245 for directories 36, 245 caching 13 CD see disk cdadm index 213 cdadm attach 215 cdadm byebye
Index contains views (views dialog) 72 contains volumes (views dialog) 72 contents dialog 112 conventions 12 cvtree 217 D data cache 40, 245 data cache set-up CLI 43 GUI 42 dcheck 126 demo mode 31 detach 218 detach button 100 device add 91 attach E Excluded volumes (Views-Dialog) 73 export 226 F CLI 99 GUI 98 attach automatically 102 detach CLI 101 GUI 100 remove CLI 93 GUI 92 server.
Index purge buffer 234 verify tracks 234 write to disk 234 incremental writing 234 init 234 initializing disks 234 Inkrementelles Filesystem 151 insert 220 installation 21 UNIX 25 Windows NT 23 iotimo 124 iso9660 136 J jobnum 126 Joliet-Format 136 jukebox add 91 attach CLI 99 GUI 98 attach automatically 102 detach CLI 101 GUI 100 device type 53 overview 17, 163 remove CLI 93 GUI 92 set-up 48 jukebox set-up CLI 65 GUI 60 M Macintosh clients 83 Major Version Number 34 maxcvt 126 maxthr 126 mdelay 124 Me
Index PD see disk portno 127 purge 234 R rahead 125 raw file system 240 recorder overview 18 reject 125 remove 226 remove button 92 rename 225 reports 229 rescan 227 robot set-up 56 Rock Ridge format (rr) 68 RPC failed: cannot connect to server 216, 224 rtrack 127 S samba 83 SCSI devices 48 SCSI driver 14, 16 serial line (robot) 52 server 14 server parameters 123, 245 change (CLI) 131 change(GUI) 130 server start UNIX 90 Windows NT 87 server.
Index Windows 95 24 Windows clients 80 WORM see disk WORM-Filesystem 160 writable file system 14 writer 14, 16, 234 writer.lic 31 WWW address 9 X x000325 (disk name) 118 iXOS-JUKEMAN 2.2 User Manual Pre.
