| Skip Navigation Links | |
| Exit Print View | |
|
Sun QFS and Sun Storage Archive Manager 5.3 Reference Manual Sun QFS and Sun Storage Archive Manager 5.3 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Sun QFS and Sun Storage Archive Manager 5.3 Reference Manual Sun QFS and Sun Storage Archive Manager 5.3 Information Library |
1. User Commands (Man Pages Section 1)
2. Maintenance Commands (Man Pages Section 1M)
3. Library Functions (Man Pages Section 3)
4. Library Functions (Man Pages Section 3X)
5. File Formats (Man Pages Section 4)
NAME
mcf - Master configuration file for Sun QFS and SAM-QFS
software
SYNOPSIS
/etc/opt/SUNWsamfs/mcf
AVAILABILITY
SUNWsamfs
SUNWqfs
DESCRIPTION
The mcf file defines the devices and family sets used by Sun
QFS and SAM-QFS software. The mcf file is read when sam-fsd
is started. You can change it at any time while sam-fsd is
running. The changes take effect when sam-fsd is restarted,
or sent the signal SIGHUP.
The following examples show an mcf file for a SAM-QFS
archiving environment and an mcf file for a Sun QFS file
system.
Example 1. The following is an example of a SAM-QFS mcf
file:
#
# SAM-QFS archiving file system configuration example
#
# Equipment Eq Eq Family Dev Additional
# Identifier Nm Tp Set St Parameters
# --------------- -- -- ------ --- ----------
samfs1 10 ms samfs1
/dev/dsk/c1t0d0s6 11 md samfs1 -
/dev/dsk/c2t0d0s6 12 md samfs1 -
#
samfs2 20 ms samfs2 - shared
/dev/dsk/c2t50020F2300000C98d0s5 21 md samfs2 -
/dev/dsk/c2t50020F2300004921d0s5 22 md samfs2 -
#
/dev/samst/c3t500104F0008E6C2Cu0 30 rb SL500 on SL500
/dev/rmt/2bn 31 tp SL500 on
/dev/rmt/3bn 32 tp SL500 on
#
/dev/rmt/0cbn 40 tp - on
#
/dev/samst/c1t3u1 50 rb ml50 on /usr/tmp/ml50_cat
/dev/rmt/2cbn 51 tp ml50 on
#
Example 2. The following is an example of a Sun QFS mcf
file:
#
# Sun QFS file system configuration example
#
# Equipment Eq Eq Family Dev Additional
# Identifier Nm Tp Set St Parameters
# ---------------- -- -- ------ --- ----------
#
qfs1 10 ma qfs1
/dev/dsk/c1t1d0s3 11 mm qfs1 -
/dev/dsk/c2t1d0s3 12 mm qfs1 -
/dev/dsk/c3t1d0s3 13 md qfs1 -
/dev/dsk/c4t1d0s3 14 md qfs1 -
#
qfs2 20 ma qfs2
/dev/dsk/c1t50020F2300000C98d0s0 21 mm qfs2 -
/dev/dsk/c1t50020F2300004921d0s0 22 mm qfs2 -
/dev/dsk/c2t50020F2300004655d0s1 23 g0 qfs2 -
/dev/dsk/c3t50020F230000651Cd0s1 24 g0 qfs2 -
/dev/dsk/c2t50020F2300004655d0s2 25 g1 qfs2 -
/dev/dsk/c3t50020F230000651Cd0s2 26 g1 qfs2 -
#
qfs3 30 ma qfs3 - shared
/dev/dsk/c2t50020F2300000C98d0s2 31 mm qfs3 -
/dev/dsk/c2t50020F2300004921d0s2 32 mm qfs3 -
/dev/dsk/c2t50020F2300000C98d0s3 33 mr qfs3 -
/dev/dsk/c2t50020F2300004921d0s3 34 mr qfs3 -
#
Example 3. The following is an example of a Sun QFS mcf
file within a SAN environment:
#
# Sun QFS file system configuration example
#
# Equipment Eq Eq Family Dev Additional
# Identifier Nm Tp Set St Parameters
# ---------------- -- -- ------ --- ----------
#
qfs1 10 ms qfs1 -
/dev/dsk/c5t16d0s0 11 md qfs1 -
/dev/dsk/c5t17d0s0 12 md qfs1 -
/dev/dsk/c5t18d0s0 13 md qfs1 -
/dev/dsk/c5t19d0s0 14 md qfs1 -
/dev/dsk/c5t20d0s0 15 md qfs1 -
/dev/dsk/c5t21d0s0 16 md qfs1 -
#
As the preceding examples show, each line in the mcf file is
divided into six fields. The format of the fields in the
mcf file is as follows:
Equipment Equipment Equipment Family Device Additional
Identifier Number Type Set State Parameters
The Equipment Identifier, Equipment Number, and Equipment
Type fields are required for each entry. The mcf file can
contain comments. Each comment line must begin with a pound
character (#). Blank lines are ignored. The fields in the
file must be separated by white space. A dash character (-)
can be used to indicate a field with no entry.
This man page describes the content of a Sun QFS or SAM-QFS
mcf file. For more configuration information, see the Sun
QFS File System Configuration and Administration Guide.
After your Sun QFS or SAM-QFS software is installed, you can
see more examples of mcf files in the following directory:
/opt/SUNWsamfs/examples
mcf File Fields
This section defines the fields in the mcf file. Note that
Sun QFS (non-archiving) environments do not include
removable media devices in their mcf files.
When writing the mcf file, group together the lines that
define similar devices. For example, create this file such
that the devices for a file system appear on consecutive
lines and devices for a library appear in a separate set of
consecutive lines.
o The Equipment Identifier specifies a file system and its
disk devices or it specifies the devices associated with
an automated library.
- For file system definition lines, this field can
contain two types of entries. The first line in a
file system definition must contain the file system
name in the Equipment Identifier field, and it must
be no longer than 31 characters in length. The file
system name specified must be identical to the
content of the Family Set field. For example:
Equipment Equipment Equipment Family Device Addl
Identifier Number Type Set State Params
---------- ------- --------- ------ ------ ------
samqfs1 1 ms samqfs1 - -
Subsequent lines in the mcf file define disk devices
to be included in the file system. The Equipment
Identifier fields in these lines can be no longer
than 127 characters in length.
- For automated library definition lines, the Equipment
Identifier field contains drive identifier
information and can be no longer than 127 characters
in length. For example:
Equipment Equipment Equipment Family Device Addl
Identifier Number Type Set State Params
---------- ------- --------- ------ ------ ------
/dev/rmt/0cbn 61 tp 9730 on -
o The Equipment number field contains a unique number for
each disk or removable media device configured. The
number you specify must be in the following range:
1 < Equipment_number < 65534
Oracle Corporation recommends that you use low numbers in
order to keep the internal software tables small.
o The Equipment Type field contains a 2-character code that
specifies the device being defined as either a disk in a
file system or as a removable media device. This man page
includes information on appropriate codes.
o The Family Set name is an arbitrary name that you select
when the mcf is created. This field can be no longer than
31 characters in length. The Family Set name defines and
associates related groups of devices. This can be either
a file system name, an automated library identifier, or a
dash character (-), as follows:
- If it is a file system name, all disk devices in the
file system must use the same file system name in
this field.
- If it is an automated library identifier, the library
and all its associated drive devices must use the
same identifier.
- If it is a standalone removable media device, use a
dash (-) character in this field.
o The Device State field defines the default status for the
device at the time the system reads the mcf file. Valid
values are as follows: on (default), off, unavail, or
down. This field is used for disk devices, libraries,
drives, and other devices.
o The Additional Parameters field provides additional
information. It can contain the path to a library catalog
file, an interface file, or other configuration
information. The Additional Parameters field can be no
longer than 127 characters. For example, this field can
be used to specify a nondefault location for the library
catalog file. If mcf file is being configured on a
SunCluster node running HA-SAM, this field must specify
the library catalog file in default location. In HA-SAM
configuration /var/opt/SUNWsamfs/catalog is linked to
cluster filesystem which is shared among all nodes within
the SunCluster.
File System Disks
When defining a disk cache family set, the following entries
define a Sun QFS or SAM-QFS file system:
ms A Sun QFS or SAM-QFS disk cache family set with no meta
devices. Metadata resides on the data device(s).
ma A Sun QFS or SAM-QFS disk cache family set with one or
more meta devices. Metadata resides on these meta
devices. File data resides on the data device(s).
A maximum of 252 separate magnetic disk devices can be
defined for each ms or ma disk cache family set.
The Family Set field is required for file system disks. It
is used to define the magnetic disks that make up the family
set. For a magnetic disk device, the Family Set field entry
must match a Family Set defined on an ms or ma entry.
The keyword shared must be specified in the Additional
Parameters field if the file system is a shared file system.
A shared file system is built by using the -S option to the
sammkfs(1M) command. For more information on this option,
see the sammkfs(1M) man page.
For each disk device, the Equipment Identifier field is the
path to a special file, such as /dev/dsk/cntndnsn. If the
meta devices are not present on the clients in a shared file
system, the keyword nodev must be specified in the Equipment
Identifier field for the mm devices.
The following equipment types are used to define the disk
devices that reside within an ms or ma file system:
mm A magnetic disk that is part of an ma disk cache
family set. Metadata is allocated on this device.
At least one mm device is required in an ma file
system.
md A magnetic disk that is part of an ms or ma disk
cache family set. This device stores file data
allocated in small Disk Allocation Units (DAUs) of 4
kilobytes and large DAUs of 16, 32, or 64 kilobytes.
The default is 64 kilobytes. In an ms family set,
this device stores both metadata and file data. In
an ma family set, this device stores only file data.
At least one md or mr device is required in an ma
file system.
mr A magnetic disk that is part of an ma disk cache
family set. This device stores file data allocated
in large Disk Allocation Units (DAUs) that are a
multiple of 8 kilobytes in a fully adjustable range
from 8 to 65528 kilobytes. The default is 64
kilobytes. File data is allocated on this device.
At least one mr or md device is required in an ma
file system.
gXXX A magnetic disk that is part of an ma disk cache
family set. The XXX identifies a striped group of
devices. This device stores file data allocated in a
large DAU size multiplied by the number of members in
the striped group. The DAU size is a multiple of 8
kilobytes in a fully adjustable range from 8 to 65528
kilobytes. The default is 256 kilobytes. The XXX
must be a decimal number in the XXXphysical size.
It is not possible to use the samgrowfs(1M) command
to increase the size of a striped group. However, it
is possible to add additional striped groups.
The Equipment Identifier is used during the mount(1M)
process as the Device To Mount. The Device To Mount is the
first field in /etc/vfstab file for the mount point. For
more information on this, see the mount(1M),
mount_samfs(1M), or vfstab(1M) man pages.
SCSI-attached Libraries
Several identifiers can be used to define SCSI-attached
libraries in the mcf file. For each SCSI-attached library,
the Equipment Identifier field must contain the path (such
as /dev/samst/cntnun) to the special file for the device
created by the samst device driver. For more information on
the device driver, see the samst(7) man page.
The Family Set field is required. It is used to associate
the library controller with the drives in the library. All
devices associated with the library must have the same
Family Set name.
The Additional Parameters field is optional. This field can
be used to specify a nondefault location for the library
catalog file. By default, catalogs are written to
/var/opt/SUNWsamfs/catalog/family_set_name. This file is
used to store information about each piece of media in the
library. In an HA-SAM configuration, this field must
specify the library catalog file in the default location,
and /var/opt/SUNWsamfs/catalog is linked to the cluster file
system that is shared among all nodes within the Sun
Cluster.
The following Equipment Type field entries can be used to
define manually mounted or automated libraries that are
attached through a SCSI interface:
Equipment Type
Field Content Definition
rb Generic SCSI library that is automatically
configured by SAM-QFS software.
NOTE: An rb definition is preferred for all
SCSI-attached libraries. The remainder of
the library definitions in this list are
supported but are not recommended for use in
an mcf file. If a library in this list is
defined in the mcf file as rb, SAM-QFS sets
the appropriate type based on the SCSI vendor
code.
ad ADIC Scalar 448 libraries.
ae ADIC Scalar 100 libraries.
al Sun StorEdge L25 and L100 and ATL M1500 and
M2500 libraries.
as ADIC Scalar 1000 and Scalar 10K libraries.
q8 Qualstar 42xx, 62xx, 82xx, TLS and RLS series
libraries
ov Overland Data Inc. Neo Series Tape Libraries.
ac ATL Products 4/52, 2640, 7100, and P-series
tape libraries, and Sun 1800, 3500, L1000 and
L11000 tape libraries.
cy Cygnet optical disk libraries.
ds DocuStore and Plasmon optical disk libraries.
eb Exabyte 210, Sun L280, and ATL Products
L-series tape libraries.
e8 Exabyte X80 libraries.
hc HP L9/L20/L60 series
h4 HP SL48 and SL24 libraries.
hp Hewlett Packard optical disk libraries.
ic IBM 3570 media changer.
me Metrum and Mountain Gate libraries.
nm Fujitsu LT250 and LT270 libraries.
pd Plasmon D-Series DVD-RAM libraries.
pg Plasmon G-Series UDO/MO libraries. The
library must be configured to G-Enterprise
mode, element address scheme 1 and barcode
type 2 or 3 by using the front panel.
ml Quantum DLTx700 tape libraries.
dm Sony DMF and DMS libraries.
cs Sony CSM-20S Tape Library.
sl Spectra Logic and Qualstar tape libraries.
s3 Sun StorageTek SL3000 library series.
s9 StorageTek 97xx series libraries.
sn StorageTek L20, L40, L80, and L500 tape
libraries and Sun StorEdge L7 and L8
autoloaders.
c4 Quantum PX500 and Sun StorEdge C4 libraries.
These libraries are supported in native mode
(PX500) only. SAM-QFS does not support these
libraries in M1500 emulation mode.
il IBM 3584 tape libraries.
Network-attached Libraries
This subsection describes how to define a network-attached
library in your mcf file.
For each Network-attached library, the Equipment Identifier
field must contain the path to the "parameters file" for the
device.
The Family Set field is required. It is used to associate
devices with the library. All devices associated with the
library must have the same Family Set name.
The Additional Parameters field is optional. This field can
be used to specify a nondefault location for the library
catalog file. By default, catalogs are written to
/var/opt/SUNWsamfs/catalog/family_set_name. This file is
used to store information about each piece of media in the
library. In an HA-SAM configuration, this field must
specify the library catalog file in the default location,
and /var/opt/SUNWsamfs/catalog is linked to the cluster file
system that is shared among all nodes within the Sun
Cluster.
The network-attached library definitions are as follows:
Equipment Type
Field Content Definition
gr ADIC/GRAU Network-attached library. The
Equipment Identifier field must contain the
path to the parameters file for the grauaci
interface. For more information, see the
grauaci(7) man page.
im IBM 3494 interface. The Equipment Identifier
field must contain the path to the parameters
file for the ibm3494 interface. For more
information, see the ibm3494(7) man page.
pe Sony network-attached interface. The
Equipment Identifier field must contain the
path to the parameters file for the sony
interface. For more information, see the
sony(7) man page.
sk StorageTek ACSLS interface. The Equipment
Identifier field must contain the path to the
parameters file for the ACSLS interface. For
more information, see the stk(7) man page.
The Historian
The hy identifier in the Equipment Type field identifies the
SAM-QFS historian.
The Equipment Identifier field must contain the string
historian.
The Family Set must contain a dash character (-).
The Additional Parameters field is optional. This field can
be used to specify a nondefault location for the historian.
By default, the historian is written to
/var/opt/SUNWsamfs/catalog/historian. This file is used to
store information about the media handled by the historian.
For more information, see the historian(7) man page.
Optical Disk Drives
This subsection describes the optical disk drive devices
supported by SAM-QFS.
NOTE that optical disk drive devices are not supported on
x64 platforms.
In the mcf file, a line describing an optical device must
contain the following:
o The Equipment Identifier field must be the path to the
special file, such as /dev/samst/cntnun, for the samst
device driver. For more information, see the samst(7) man
page.
o The Family Set field is used to associate the drive with
the library that has the same Family Set. If the family
set is defined as a dash (-), the drive is assumed to be
manually loaded.
o The Equipment Type field contains the optical drive
identifier, as follows:
Equipment Type
Field Content Definition
od Generic optical disk. A disk that is
automatically configured by SAM-QFS. If
you specify od, SAM-QFS sets the
appropriate type based on the SCSI vendor
code.
NOTE that an od definition is preferred for
all optical drives. If you specify od in
the Equipment Type field, the SAM-QFS
software sets the appropriate type based on
the SCSI vendor code. The remainder of the
definitions in this list are supported but
are not recommended for use in an mcf file.
o2 12 inch WORM drive.
wo 5 1/4 inch optical WORM drive.
mo 5 1/4 inch erasable optical drive. The
SAM-QFS environment supports disks with
512-, 1024-, and 2048-byte sectors.
pu Plasmon UDO drive.
mf IBM Multi Function optical drive.
Note that for all magneto-optical media, the default archmax
value is 5 megabytes.
Tape Drives
This subsection describes the set of tape drives supported
by SAM-QFS software for use in manually mounted and
automated libraries.
A line in the mcf file for a tape drive must contain
information in the following other fields:
o The Equipment Identifier must be the path to the raw
device, typically, /dev/rmt/nbn. However, it can be any
symbolic link that also points to the proper special file
in the /devices tree. You must specify the BSD no-rewind
path.
If the device supports compression, then that path should
be specified for better tape usage; except if the
ST_AUTODEN_OVERRIDE drive option bit is set in an st.conf
entry, you cannot specify a compression preference by
changing the dev entry. Any attempt to specify
compression is ignored. This is determined by the Solaris
SCSI tape driver, st. The compression state of the drive
is determined by its power-on default.
For more information, see the mtio(7) man page.
o The Family Set field must be used to associate the device
with the library that has the same Family Set name. If
the family set is a dash character (-), then the device is
assumed to be a manually loaded device.
o The Additional Parameters is required for a tape drive if
the Equipment Identifier field does not contain
information in a /dev/rmt/* format (the standard st device
driver). If specified, the Additional Parameters field
must contain the path to the special file, such as
/dev/samst/cntnun, for the samst device driver. For more
information, see the samst(7) man page.
If SAM-QFS has access to a tape device, no other user should
be allowed access the device during that period. SAM-QFS
changes the mode on the path supplied in the mcf file to
0660 at startup, or when the device state moves from down to
on. When the state moves from on to down, the mode is set
to the value of tp_mode in the defaults.conf file. For more
information, see tbe defaults.conf(4) man page.
The following list shows the tape drives for each type of
tape media supported. The tape drives supported by SAM-QFS
are as follows:
Equipment Type
Field Content Definition
tp Generic tape drive. These tapes are
automatically configured by SAM-QFS.
NOTE that a tp definition is preferred for
all tape drives. If you specify tp in the
Equipment Type field, the SAM-QFS software
sets the appropriate type based on the SCSI
vendor code. The remainder of the
definitions in this list are supported but
are not recommended for use in an mcf file.
dt DAT 4mm tape drive. In the defaults.conf
file, the default block size keyword for this
media is dt_blksize = 16.
lt Digital linear tape (DLT) drive (including
Super DLT and DLT-S4). In the defaults.conf
file, the default block size keyword for this
type of media is lt_blksize = 128.
xt Exabyte (850x) 8mm tape drive. In the
defaults.conf file, the default block size
keyword for this media is xt_blksize = 16.
xm Exabyte Mammoth-2 8mm tape drive. In the
defaults.conf file, the default block size
keyword for this media is xm_blksize = 128.
fd Fujitsu M8100 128-track tape drive. In the
defaults.conf file, the default block size
keyword for this media is fd_blksize = 256.
i7 IBM 3570 tape drive. In the defaults.conf
file, the default block size keyword for this
media is i7_blksize = 128.
li IBM 3580, Seagate Viper 200 and HP Ultrium
(LTO) In the defaults.conf file, the default
block size keyword for this media is
li_blksize = 256.
ib IBM 3590 tape drive. In the defaults.conf
file, the default block size keyword for this
media is ib_blksize = 256.
m2 IBM 3592 J1A and E05 tape drives. In the
defaults.conf file, the default block size
keyword for this media is m2_blksize = 2048.
vt Metrum VHS (RSP-2150) tape drive. In the
defaults.conf file, the default block size
keyword for this media is vt_blksize = 128.
at Sony AIT tape drive. In the defaults.conf
file, the default block size keyword for this
media is at_blksize = 128.
sa Sony Super AIT tape drive. In the
defaults.conf file, the default block size
keyword for this media is sa_blksize = 2048.
so Sony DTF tape drive. In the defaults.conf
file, the default block size keyword for this
media is so_blksize = 1024.
st StorageTek 3480 tape drive. In the
defaults.conf file, the default block size
keyword for this media is st_blksize = 128.
se StorageTek 9490 tape drive. In the
defaults.conf file, the default block size
keyword for this media is se_blksize = 128.
sg StorageTek 9840 tape drive. In the
defaults.conf file, the default block size
keyword for this media is sg_blksize = 256.
d3 StorageTek D3 tape drive. In the
defaults.conf file, the default block size
keyword for this media is d3_blksize = 256.
sf StorageTek T9940 tape drive. In the
defaults.conf file, the default block size
keyword for this media is sf_blksize = 256.
ti StorageTek Titanium tape drive. In the
defaults.conf file, the default block size
keyword for this media is ti_blksize = 2048.
For all tapes, the SAM-QFS system sets the block size to a
media-specific default. For information on how to change
the default block size, see the defaults.conf(4) man page.
For all tapes, the default archmax value is 512 megabytes.
Disk Archiving
The archiver can be configured to archive directly to online
disk cache. To enable disk archiving, you must perform the
following steps:
1. Create directories in online disk cache to serve as
destinations for the archive copies.
2. Create the /etc/opt/SUNWsamfs/diskvols.conf file.
3. Edit the archiver.cmd file and add the -disk_archive
directive.
The media type for a disk volume is dk. The block size for
a disk volume is dk_blksize=1024. This value cannot be
changed.
The media type for a Sun StorageTek 5800 Storage System disk
volume is cb. The 5800 schema specifies the metadata
attributes that are stored with objects in the 5800 system.
The system comes preconfigured with a default metadata
schema. For a 5800 disk volume you must modify the default
schema file to add metadata specific to SAM-QFS. For more
information on configuring the schema, refer to the Sun
StorageTek 5800 System Administration Guide. The file
/opt/SUNWsamfs/examples/metadata_config_samfs.xml can be
used to extend the default schema for SAM-QFS.
Disk archiving is explained in more detail in the Sun
Storage Archive Manager Installation and Configuration Guide
and in the Sun Storage Archive Manager Configuration and
Administration Guide.
SAM-Remote Device Definitions
Several identifiers define devices when using the Sun
SAM-Remote client or Sun SAM-Remote server software. For
more information on configuring the Sun SAM-Remote client or
the Sun SAM-Remote server, see the sam-remote(7) man page or
see the Sun SAM-Remote Administrator's Guide.
The identifiers used when configuring the Sun SAM-Remote
client or Sun SAM-Remote server are as follows:
Equipment Type
Field Content Definition
ss Sun SAM-Remote server. The Equipment
Identifier field must contain the path name
to the server configuration file. The Family
Set field must identify the server. That is,
it must be the same as the Family Set name of
the server. It must match the name used in
the client side definition. It is used by
the clients to associate the device with the
server of the same Family Set name.
sc Sun SAM-Remote client. The Equipment
Identifier field must contain the path name
to the client configuration file. The Family
Set field must contain an identifier that is
the same as the family set name of the
server. It is used by the clients to
associate the device with the server of the
same Family Set name. The Additional
Parameters field must contain the full path
name of the client's library catalog file.
rd Sun SAM-Remote pseudo-device. The Equipment
Identifier field must be the path to the
pseudo-device, such as /dev/samrd/rd2. The
Family Set field must be the name of the
server. It is used by the clients to
associate the device with the server of the
same Family Set name.
FILES
/opt/SUNWsamfs/examples Contains example mcf files.
SEE ALSO
Sun SAM-Remote Administrator's Guide.
Sun QFS File System Administration Guide.
Sun Storage Archive Manager Administration Guide.
chmod(1).
build_cat(1M), dump_cat(1M), mount(1M), mount_samfs(1M),
sammkfs(1M). sam-fsd(1M),
defaults.conf(4), inquiry.conf(4), vfstab(4).
dst(7), fujitsulmf(7), grauaci(7), historian(7), ibm3494(7),
mtio(7), sam-remote(7), samst(7), sony(7), st(7), stk(7).
|