1.2 License Registration
AdvFS is the file system default on the operating system.
AdvFS Utilities
is a separately licensed product that provides additional processing capabilities.
Before you can use the file system utilities, you must register a license
The AdvFS file system consists of two distinct layers: the directory
hierarchy layer and the physical storage layer.
The directory hierarchy layer
implements the file-naming scheme and POSIX-compliant functions such as creating
and opening files, or reading and writing to files.
The physical storage layer
implements write-ahead logging, caching, file allocation, and physical disk
I/O functions.
The decoupled file system structure enables you to manage the physical
storage layer apart from the directory hierarchy layer.
This means that you
can move files between a defined group of disk volumes without changing pathnames
for your files.
Because the pathnames remain the same, the action is completely
transparent to end users.
AdvFS implements two unique file system concepts:
AdvFS can incorporate Logical Storage Manager (LSM) volumes into the
file system structure.
When AdvFS is configured with LSM, file system reliability
and availability improve because AdvFS can take advantage of LSM features
(see
Section 1.10).
A fileset follows the logical structure of a traditional UNIX
file system.
It is a hierarchy of directory names and file names, and it is
what you mount on your system.
AdvFS goes beyond the traditional file system
by allowing you to create multiple filesets that share a common pool of storage
called a domain.
See
Section 1.7
for more information about
filesets.
A domain represents the physical storage layer.
It is managed separately
from the directory structure.
You can add or remove volumes without affecting
the directory structure.
See
Section 1.6
for more information
about domains.
A
The AdvFS file system is a log-based file system that employs
When you create a domain, AdvFS creates a transaction log file for it.
During crash recovery, AdvFS reads the transaction log file to confirm file
system transactions.
All completed transactions are committed to disk and
uncompleted transactions are undone.
The number of uncommitted records in
the log, not the amount of data in the file system, dictates the speed of
recovery.
This means that recovery usually takes only a few seconds.
Traditional
UNIX file systems rely on the
By default, only file system structures are logged, but you can choose
to log file data and change the way your system writes to storage (see
Section 4.4).
A file that has data logging turned on remains internally
consistent in the event of a system crash.
However, enabling data logging
can slow system performance.
Files are not static; their space requirements change over time.
To
maintain contiguous file placement without overallocating space on the disk,
AdvFS uses a unique file storage allocation scheme.
Key features of file storage allocation are:
Extents
An
File I/O is most efficient when there are few extents.
If a file consists
of many small extents, it takes more I/O processing to read or write that
file.
Given the dynamic nature of a file system, the file storage allocation
cannot always guarantee contiguous placement of pages.
The following factors
affect placement:
Excessive disk fragmentation
When a disk is fragmented there are many small free spaces, so AdvFS
writes data to isolated physical pages, based on availability, instead of
writing to contiguous pages.
This might result in files with many extents.
Multiple users
When there are many users on a system, requests for space increase,
decreasing the likelihood of contiguous file allocation.
If you have a domain with files containing many extents, you can decrease
the number by running the
Preallocation
Each time a file is appended, AdvFS adds pages to the file by preallocating
one-fourth of the file size, up to 16 pages.
Excess preallocated space is
truncated when the file is closed.
For multivolume domains, new files are allocated sequentially across
volumes.
Volumes that are more than 86% full (allocated) are not used for
new file allocation unless all volumes are more than 86% full.
When data is
appended to existing files, storage is allocated on the volume on which the
file was initially allocated until the volume is full.
Fragments
AdvFS writes files to disk in sets of 8 KB pages.
In files where holding
the last bytes in an 8 KB page would represent a waste of more than 5% of
the allocated space, a
Sparse files
A
You can create a sparse file by setting a file's end-of-file using the
Core files are sparse files.
They have large areas with no information
and do not use disk blocks for locations where no data exists.
Quota files
are sparse because they are indexed by user ID.
If there are gaps in the user
IDs, there might be sections of the file with no data.
In contrast, database applications generally reserve storage for the
entire file even when data is not available.
The applications generally write
zeroes in the pages that have no useful data.
By writing the data sequentially,
the database application creates a database file with large sets of contiguous
pages and a small number of extents.
To examine the length of a sparse file, including the pages that do
not have disk storage, use the
When planning your configuration, consider setting up the
You can set up AdvFS to resemble a traditional UFS configuration with
one partition (volume) per domain and one fileset in each domain.
If you have
the optional AdvFS Utilities, when you need space, you can add volumes (except
to the local root which is restricted to one volume) to increase the size
of the domain without changing anything in the existing configuration.
An active AdvFS file system requires one domain and one mounted fileset.
To create an active domain:
Create a domain and assign a volume to it (see
Section 1.6.5).
Create a fileset (see
Section 1.7.4).
Create a mount-point directory (see
Section 1.7.6).
Mount a fileset (see
Section 1.7.6).
You can create one fileset per domain or you can create many.
See
Section 1.6.1
and
Section 1.7.1
for guidelines.
AdvFS is fully supported in the
See
Appendix B
for a complete list of AdvFS commands.
For more detailed information on AdvFS configuration, see
System Configuration and Tuning.
An AdvFS volume can be a raw disk partition, an entire disk, an aggregate
volume provided by LSM, or a hardware or software redundant array of independent
disks (RAID) storage.
Each volume in an AdvFS domain contains a
A volume can be assigned to only one domain.
It is associated with its
domain by a
If you have the optional AdvFS Utilities, you can add volumes to create
a multivolume domain.
Multivolume domains increase the storage available for
the filesets and allow for preventative disk maintenance.
You can add volumes
immediately after creating the domain, even before creating and mounting filesets.
To perform preventative disk maintenance, you can add a new volume to the
domain, migrate your files to the new volume, and then remove the old volume.
For AdvFS to function properly, the number of volumes in a domain with
the same domain ID must remain consistent with the number of volumes stored
in the domain-attributes record.
In addition, each domain is defined by an
entry in the
To reuse a volume see
Section 5.8.1.
You can configure AdvFS volumes with attributes that determine how data
is read, cached, written, and consolidated.
When an AdvFS volume is incorporated
into a domain, either by creating the initial domain or by adding a volume,
the default volume attributes are set.
Modifying these default attributes
might improve performance in some system configurations.
You can run the
To display or modify the current volume attributes, use the SysMan Manage
an AdvFS Domain utility, or enter the
See
Chapter 4
and
System Configuration and Tuning
for more
complete information on modifying attributes to improve system performance.
A domain is the physical storage layer of the AdvFS file system.
It
is a defined pool of physical storage that can contain one or more volumes.
Because this storage is managed separately from the directory structure (see
Section 1.6.2), you can expand and contract the size of the domain
by adding or removing volumes.
You can move files between volumes in the domain
without changing file pathnames.
Changing the name of the domain does not
affect the domain ID.
The domain name is defined by a directory entry in the
Domain names
must be unique.
You cannot use slash (/), number (#), colon (:), asterisk
(*), question mark (?), tab, newline, form feed, return, vertical tab, and
space characters in a domain name.
How you configure domains depends on your organization's needs.
You
can assign all available storage to a few domains or you can group specific
partitions or disks into many domains.
You must also take into account how
you configure your filesets (see
Section 1.7.1).
With AdvFS
Utilities, you can assign multiple volumes to a domain and distribute the
filesets and files across the volumes.
Establishing multiple domains allows greater control over your physical
resources.
You can create domains for use by specific projects, groups of
users, departments, or any division that makes sense for your organization.
For example, you could create domains for each of your organization's departments,
such as engineering, finance, and personnel.
There are a number of factors to consider when configuring domains:
To maintain high performance, do not split a disk between
two domains.
For example, do not add partition
Adding one partition containing the entire disk (typically,
partition
Assuming the disks are the same type and speed, it is generally
more efficient to spread your domain over several disks.
For example, a domain
with three volumes on separate disks is more efficient than one with three
partitions on a single disk because the latter has only one I/O path.
Creating a domain on several volumes can increase the defragmentation
speed because the
Combining multiple volumes within a single domain allows you
to build larger domains and reduces the overall management effort because
fewer domains require less administration.
However, a single volume failure
within a domain renders the entire domain inaccessible.
Limiting the number of volumes decreases the risk of disk
errors that can cause the entire domain to become inaccessible.
To improve
reliability, you can set up LSM
The
System Configuration and Tuning
guide provides detailed guidelines for
planning and configuring your file system.
System Limits
lists the limits for the AdvFS file system.
The SysMan Manage an AdvFS Domain
utility allows you to create and configure domains.
See
Appendix D
to configure your domains using a graphical user interface.
The
AdvFS automatically creates and maintains this directory when you use
standard AdvFS commands.
You must have a current
When you create a domain, a soft link is created from the domain entry
in the
Back up the
If you attempt to mount a fileset from a domain with a damaged directory,
a message similar to the following for the domain
If the
Domains in Version 5.0 and later of the operating system have an improved
disk structure that provides support for quota values larger than 2 terabytes
and increases performance for directories containing thousands of files.
You
do not need to adjust bitfile metadata table (BMT) allocations.
All domains
that were created in operating systems prior to Version 5.0 are recognized by later
versions but are not automatically upgraded to the new structure.
A
You can mount a DVN3 fileset on a system running Version 5.0 or later.
You
cannot locally mount a fileset in a DVN4 domain created under Version 5.0 or later
on a system running a Version 4 operating system.
If you need to access a
DVN4 fileset while running an earlier version of the operating system, NFS
mount it from a server running Version 5 or later software (see
Section 5.4).
Therefore, if your application requires backward compatibility, you should
not upgrade your domain to the new DVN.
See
Section 5.4.1
for a discussion of utility incompatibility.
All domains created on Version 5.0 and higher operating systems have a DVN
of 4.
Therefore, if you do a full installation, all the domains created in
the process have the new structure.
If you perform an update installation from a system running a Version
4 operating system, all existing domains retain the DVN of 3.
This means that
If you are running an application that requires quota limits larger
than 2 terabytes or that uses directories containing thousands of files, you
can improve performance by upgrading your old domain to a DVN4 domain.
DVN4
domains automatically have an index created when the directory grows beyond
a page, that is, about 200 files.
Use the
To upgrade a domain, create a new domain on a system running Version 5.0
or later software and copy all the information from the old domain to it.
If you are unfamiliar with creating domains, read
Section 1.6.5
first.
To upgrade a domain:
Back up the filesets in the domain to tape by using the
Remove the old domain by using the
Create a new domain by using the
Create the new filesets by using the
Restore the filesets in the new domain by using the
For example, to upgrade the domain
You can create DVN3 domains on a Version 5 system.
They are recognized
by earlier versions of the operating system.
See
If a domain is active (at least one fileset is mounted), you can display
detailed information about the domain and the volumes included in it by using
the
For example, to display domain information for the
The first step in setting up an AdvFS file system is creating a domain
and assigning an initial volume to it.
However, a domain is not a complete
file system that you can mount.
In order to mount an AdvFS file system, the
domain must contain one or more filesets.
You can access files as soon as
you mount one or more filesets (see
Section 1.7).
Creating a single-volume domain with a single fileset is equivalent
to creating a traditional UFS file system.
To set up an active, single-volume
file system, as illustrated in
Figure 1-2, use the
SysMan Create a New AdvFS Domain utility, a graphical user interface (see
Appendix D), or enter the
To create an active single-volume DVN4 domain:
Create a single-volume domain associated with a volume by
using the
Create one or more filesets by using the
Create the mount-point directory by using the
Mount each fileset by using the
For information about creating a DVN3 domain, see
Do not use the
The following example creates a single-volume DVN4 domain,
You can set up a domain with an LSM storage by specifying an LSM volume.
See
Section 1.10
for information about using AdvFS with LSM.
If you have AdvFS Utilities, you can change the size of your domain by adding
more volumes.
You can transform a single-volume domain (except the root domain)
into a multivolume domain (see the Sysman Manage an AdvFS Domain utility,
Section 1.6.6
and
Appendix D).
If you try to create a domain on a volume that is marked on the disk
as in use in the disk label, the
You can expand a domain by replacing one of the volumes in the domain
with a larger storage device or, if you have AdvFS Utilities, by adding another
volume to the domain.
Figure 1-3
shows a graphic illustration
of adding volumes to a domain.
Neither adding nor removing volumes affects
the directory hierarchy layer; all pathnames for the files remain the same.
Also, the file system can remain active during the disk exchange.
There might be performance benefits if, instead of increasing the size
of a DVN3 domain, you upgrade to the new file structure (see
Section 1.6.3)
and then increase its size.
If your domain is located on an LSM volume, do not use the LSM
A newly created domain consists of one volume, which can be a disk,
disk partition, or logical volume.
To add volumes, use the SysMan Manage an
AdvFS Domain utility, a graphical user interface (see
Appendix D),
or enter the
For example, to add volume
You can add volumes immediately after creating a domain, or you can
wait until the domain requires additional space.
You can add a volume to an
active domain while its filesets are mounted and in use.
You cannot add a volume to the root domain unless you are running a
cluster (see
Cluster Administration).
If you are running
a cluster configuration, you add another root volume the same way that you
add any volume.
If you are not running a cluster and need to increase the
size of the root domain, follow the procedure for recovering from a failure
of the root domain (see
Section 5.11) and attach a larger
volume.
Do not use the
If you do not have AdvFS Utilities and want to increase the size of
your domain:
Make a new domain on the new larger device.
Do not use the
same name for the domain.
Create filesets with the same name as the old filesets.
Create a temporary mount-point directory for each fileset.
Mount each new fileset on its temporary mount point.
Use a utility (for example
Unmount the old and new filesets.
Rename the new domain to the old name if you want.
If you
do not change the domain and fileset names, you do not need to to edit the
Mount each new fileset using the mount point of the old fileset.
The directory tree is then unchanged.
Delete all temporary mount-point directories.
To increase the size of a domain if you have AdvFS Utilities:
Optionally, use the
Add the new volume to the domain.
Remove the old volume if you do not want it.
Optionally, run the
The following example replaces one disk, the volume
AdvFS does not add a volume that causes partitions to overlap
with a volume that is mounted for another file system, a swap area, or a reserved
partition.
To add an overlapping partition, unmount all filesets and use the
Disabling the overlap check can result in extensive data loss and should
be used with extreme caution (see
When there is sufficient free space on the remaining volumes, you can
remove volumes from a domain without interrupting users or affecting the logical
structure of the filesets in the domain.
The file system automatically migrates
the contents of the selected volume to other volumes in the domain.
Before
you can remove a volume from a domain, all filesets in the domain must be
mounted.
You get an error if you try to remove a volume from a domain with
unmounted filesets.
If there is not enough free space on other volumes in the domain to
accept the files that are offloaded from the departing volume, as many files
as possible are moved to available free space on other volumes.
Then, a message
is sent indicating that there is insufficient space.
The domain is not damaged.
If your domain is located on an LSM volume, do not use the LSM
To remove a volume, use the SysMan Manage an AdvFS Domain utility, a
graphical user interface (see
Appendix D), or enter the
For example, to remove
You can interrupt the
Under some circumstances interrupting an
To reduce the size of a domain:
Use the
Remove the volume.
Run the
You cannot remove a volume from a domain that you are balancing or defragmenting.
The following example illustrates how to remove one disk of the
If you remove an AdvFS volume that contains a stripe segment, the
You can remove a domain after all filesets in the domain are unmounted.
When you remove a domain, the entry in the
Removing the domain to inactivate filesets instead of using the
To remove a domain, use a graphical user interface (see
Appendix D),
or unmount all filesets and fileset clones from the command line.
Then, enter
the
For example, to remove the domain
If you use this command when there are mounted filesets, the system
displays an error message.
AdvFS does not remove an active domain.
You can assign a new name to an existing domain without altering its
domain ID.
When you rename a domain, entries for all filesets in the domain
must be updated in the
Unmount all the filesets and any related clones.
In the
Edit the
Mount the filesets in the renamed domain.
For example, to rename the domain
Locate the following in the
Edit this line as follows:
Mount the fileset:
A fileset represents a mountable portion of the directory hierarchy
of a file system.
Filesets and traditional UNIX file systems are equivalent
in many ways.
You mount AdvFS filesets.
Filesets contain files, are units
on which you enable quotas, and are units for backing up data.
In contrast with traditional file systems, the directory hierarchy
of AdvFS is independent of the storage.
Therefore, you can change file placement
without affecting the logical structure of the filesets.
Fileset names can be associated with their domain names, as in
Fileset names must be unique within a domain.
Each fileset has a unique
AdvFS also supports
Fileset
names must be unique.
You cannot use slash (/), number (#), colon (:), asterisk
(*), question mark (?), tab, newline, form feed, return, vertical tab, and
space characters.
Filesets that are not in the same domain can have the same
name.
The filesets in a domain share the available space on the volumes in
the domain and use the same domain transaction log file.
Each fileset has
its own directory structure, root tag directory, quota files, and frag file.
The optimal number of AdvFS filesets in a domain depends primarily on the
requirements of the applications that use the filesets.
It is generally a good idea to have multiple filesets rather than one
large fileset.
Whether you place these filesets in a number of domains rather
than in one large domain depends on your application.
If a fileset has critical
access requirements, place it in its own domain.
For applications that perform
many file create and remove operations, configure multiple domains, each on
its own volume.
This reduces contention related to I/O.
Create multiple smaller filesets rather than a few large filesets if
you do not want to share space between filesets.
You can then set fileset
quotas to limit resource use for each fileset.
Create filesets containing files having similar requirements in the
same domain.
For example, do not place small temporary mail news server files
in the same domain as the database.
Because filesets are managed independently of their physical storage,
each fileset can be backed up independently (see
Chapter 2)
and can be assigned its own quota limits (see
Chapter 2).
Multiple small filesets can be backed up and restored more quickly than a
single large fileset.
You can run the
You can group files in filesets by their management requirements.
For
example, you can create a fileset for developers' files that is backed up
twice a day and you can create another fileset with quotas imposed to limit
the amount of disk space available to the marketing department.
All filesets share the transaction log file in a domain, so filesets
with a large amount of I/O can cause the transaction log file to become a
bottleneck (see
Section 1.3.2).
Balance the management gains
of having multiple filesets in a domain against the potential performance
reduction you might incur by having all of the log data for all filesets going
to one transaction log file (see
Section 4.3).
You can create and mount filesets until the system runs out of system
resources (such as memory or disk space).
System Limits
contains information about this and other system limits.
System Configuration and Tuning
provides detailed guidelines and suggestions
for file system configuration.
The SysMan Manage an AdvFS Domain utility allows
you to create and configure filesets.
You can use a graphical user interface
to accomplish many configuration operations (see
Appendix D).
Add AdvFS filesets to the
The fileset entry includes the domain name, fileset name, mount point,
file system type, and the mount-point options.
If you want to enable quotas,
include the
For example, to automatically mount the
The
Any system user can display detailed information about mounted filesets
and clones.
Root user privilege is required only if the domain is inactive
(filesets unmounted).
To examine fileset information enter:
The following example displays the domain
The following example displays
You can use a graphical user interface (see
Appendix D) to
obtain similar information.
A domain must contain at least one mounted fileset to be active (see
Section 1.3.1).
Within a domain you can create multiple filesets that
share the storage pool established for the domain.
Any fileset can consume
all of the storage available in the domain.
Each fileset can be mounted and unmounted independently of the other
filesets in the domain.
You can limit fileset growth within a domain by assigning
fileset quotas (see
Chapter 2).
You can control the
creation of frags for files that waste more than 5% of their allocated storage
(see
Section 4.2).
You can set the characteristics of the fileset
at creation by using the
To create a fileset in a domain, use the SysMan Create a New AdvFS Fileset
utility, a graphical user interface (see
Appendix D), or enter the
To mount a fileset, you must create a mount-point directory for it (see
Section 1.7.6).
For example, to create the fileset
See also
Section 1.6.5, which contains examples for
configuring an active (filesets mounted) domain.
Filesets that are part of domains created for operating system software Version 5.0
and later (DVN4) support large quota values and have better performance for
very large directories.
Filesets in domains created earlier (DVN3) do not
have these improvements.
To upgrade a fileset to the new version, you must
upgrade its domain (that is, create a new one) and restore the fileset to
it.
Then the restored fileset has the new quota limits and performance improvements
(see
Section 1.6.3).
You cannot mount filesets with the new DVN on operating system versions
earlier than Version 5.0 unless you NFS mount them from a server running Version 5.0
or later of the operating system software (see
Section 5.4).
As with traditional UNIX file systems, AdvFS filesets must be mounted
in order to access them.
You must create a mount-point directory if it does
not exist.
Filesets to be mounted must be compatible with the operating system
on which they were created (see
Section 5.4).
To mount a fileset, use the SysMan General File System Utilities - Mount
File Systems utility, a graphical user interface (see
Appendix D),
or enter the
For example, to create a mount-point directory and mount the fileset
Before a fileset is mounted, AdvFS verifies that all data in all volumes
in a domain can be accessed.
If there are problems, the mount might fail or
the fileset might be mounted as read-only (see
Section 5.8.7).
If you attempt to mount a fileset with an incorrect number of volumes,
the mount operation fails.
See
Section 5.9.2
and
You can specify temporary atomic write data logging in your mount operation
(see
Section 4.4).
An error message is displayed if you attempt to mount a fileset created
under operating system software Version 5.0 or later on a system running Version
4 or earlier operating system software (see
Section 5.4).
If you unmount a fileset, the fileset remains in the domain but it is
not accessible.
Mount the fileset to make it available again.
To unmount an AdvFS fileset, use the SysMan General File System Utilities
- Dismount a File System utility, a graphical user interface (see
Appendix D),
or enter the
For example, to unmount the fileset
If you remove a fileset, it cannot be remounted.
It is no longer part
of the domain.
You must unmount a fileset and remove the fileset clone before you can
remove it.
If you have set up a trashcan directory (see
Section 1.8)
for the fileset, it is also removed.
To remove a fileset, use the SysMan Manage an AdvFS Domain utility,
a graphical user interface (see
Appendix D) or, from the command
line, enter the
For example, to remove the
The fastest way to remove all filesets is to remove the domain by using
the
An unmounted fileset can be renamed.
The fileset name is kept within
the domain and is an attribute that you assign.
When you rename a fileset,
only this assignment is changed.
The fileset ID is not altered.
To rename a fileset, unmount it and unmount its clone if it has one.
You can use the SysMan Manage an AdvFS Domain utility, a graphical user interface
(see
Appendix D) or, from the command line, enter:
After renaming the fileset, you must update the corresponding entries
in the
For example, to rename the
Locate the following line in the
Edit this line as follows:
Mount the fileset:
You cannot rename an AdvFS fileset clone.
You must delete the old clone
and create a new one.
With the
For example, to enable object safety in the
When the object safety option is enabled, the pages on disk belonging
to the fileset are zero-filled and forced to disk before they are available
to the file.
This prevents old data from being visible if a system crash occurs
while the file is being written.
Files that allocated storage just prior to enabling object safety initiate
object safety once the buffers associated with the allocation are flushed
to disk.
Because object safety degrades performance (the pages on disk are zero-filled
then the zeroes are overwritten with data) the administrator must decide if
the performance impact is worth the improved security.
If you have the optional AdvFS Utilities license, you can back up your
files using an AdvFS fileset clone.
A fileset clone is a read-only snapshot
of fileset data structures (metadata).
When you clone a fileset (create a
fileset clone), the utility copies only the structure of the original fileset,
not the actual data.
When a file is modified, the file system copies the original,
unchanged data to the AdvFS fileset clone.
(This is called
Fileset clones increase the availability of data because they:
Preserve the system at a particular time
A clone is not a replacement for the backup process (using the
Protect against accidental file deletion or corruption
Create a clone of each fileset that you plan to access or modify.
By
leaving the fileset clone on line, you can replace unintentionally deleted
or corrupt files without loading backup tapes.
A clone cannot be cloned.
See
Section 3.3
for command-line instructions on
using cloning for online backup.
See
Section D.4.3
for an explanation
of cloning with the AdvFS GUI.
Changing text files with an editor can cause the entire original file
to be copied to the clone.
Many editors rewrite the entire file regardless
of what has changed.
When this happens, your AdvFS fileset clone might grow
very large.
There is no way for AdvFS to alter this process.
When you delete a file that existed when the clone was created, it remains
available (but not visible in the original fileset) for the life of the clone.
The file is not copied to the clone, but the actual delete operation is delayed
until the clone is deleted.
The version of the file that is retained is the
one that existed when the clone was created.
Later updates are lost.
The size of an AdvFS fileset clone depends upon the number of updates
that occur during the life of the clone.
The
When a domain runs out of disk space, the file system loses its ability
to maintain the consistency of files within AdvFS fileset clones.
The original
fileset is usable, but the fileset clone is not accurate and is no longer
used.
A warning message is displayed on both the user's terminal and the system
console.
To clone a system disk and boot it on another system, see Best Practices.
This not the same as creating an AdvFS fileset clone.
AdvFS fileset cloning is transparent to the user and has little impact
on system performance.
You must be root user to create a clone.
To create
a fileset clone, use the SysMan Manage an AdvFS Domain utility, a graphical
user interface (see
Appendix D), or enter the
For example, to create a clone called
Clones are mounted and unmounted in the same manner as any other fileset
(see
Section 1.7.6
and
Section 1.7.7).
Clones are removed in the same manner as any other fileset (see
Section 1.7.8).
A fileset clone cannot be renamed.
To assign a new name, remove the
old clone and create a new clone for the fileset.
(Note that this new clone
is a snapshot of the fileset at a later point in time than the deleted clone.)
If you have the optional AdvFS Utilities, end users can configure their
systems to retain a copy of files they have deleted.
They can attach
Trashcan directories are a trade off, however.
The convenience of recovering
files without accessing backup comes at the cost of the additional writes
to disk that are required when files are deleted.
Root user privilege is not required to use this command.
However, the
following restrictions apply:
You can restore only the most recently deleted version of
a file.
You can attach more than one directory to the same trashcan
directory; however, if you delete files with identical file names from the
attached directories, only the most recently deleted file remains in the trashcan
directory.
Only files you delete directly are removed to the trashcan.
If you delete a complete fileset using the
Deleted files in an attached trashcan count against your quota.
When you delete files in the trashcan directory, they are
unrecoverable.
Table 1-1
lists and defines the commands for setting
up and managing a trashcan.
For example, to attach the trashcan directory
To remove a file, and look for it in the trashcan directory:
To remove the connection between the trashcan and the directory:
There are several advantages to configuring AdvFS for the root file
system.
You can:
Restart quickly after a crash.
You do not run the
Use one set of tools to manage all local file systems.
All
features of AdvFS except the
Use AdvFS with LSM to mirror the root file system.
This allows
your root file system to remain viable even if there is a media failure.
The following restrictions on the AdvFS root file systems are currently
enforced:
Unless you are running a cluster (see
Cluster Administration), the root domain can contain only one volume.
You cannot add
volumes to the root domain.
The volume must start from the beginning of the physical device
( The root fileset must be the first fileset created in the
root domain.
You can assign any name to the root domain and fileset but
the same name must be entered in the
The root domain should contain only the root fileset.
It is not advisable
to include the
You can put the root file system on an AdvFS volume during the initial
base system installation or you can convert your existing root file system
after installation.
Note that when you install AdvFS as the root file system
during the initial installation, root defaults to the
If you construct your own root file system, you must configure it on
the
The root file system is automatically mounted as read-only when the
system is booted in single-user mode.
You can change the root fileset mount
from read-only to read-write by using the
Use this procedure when you need to make modifications to the root configuration.
For example, use it if you need to modify your
You can change the name of the root domain the same as any other domain
(see
Section 1.6.9).
The name of a root domain is stored as the
directory name in the
Changing the name of the root fileset is similar to changing the name
of any other fileset (see
Section 1.7.9).
There are, however,
two complications:
The
You must edit the
Therefore, you must use an alternate bootable partition and manipulate
the root fileset you are changing as you would an ordinary fileset, make the
changes, then reboot the changed fileset as root.
To rename the root fileset:
Boot a partition other than the one you want to change.
(It
can be UFS.)
Make a new entry in the
Change to the new directory and make a symbolic link to the
device holding the original fileset.
Use the
Mount the newly named root fileset at a temporary location
in order to update its
Change the
Shut down the alternate system.
Reboot the original AdvFS system.
The following procedure changes the name of the root fileset from
Boot a device other than the one you want to change.
Make an entry for
Change to the new directory and make a symbolic link for
Rename the fileset from
Mount the changed root fileset to update the associated
Edit the
Locate the following line in the
Edit this line as follows:
Shut down the alternate system.
Reboot the AdvFS system.
If you change the root domain and fileset names and do not change the
Logical Storage Manager (LSM) allows you to manage all of your storage
devices, such as disks, partitions, or RAID sets as a flexible pool of storage
from which you create LSM volumes.
You can create mirrored and striped LSM
volumes and change their attributes as performance and availability needs
dictate.
For more information see
Logical Storage Manager.
AdvFS treats LSM volumes just like any other storage.
You can use LSM
to create and manage the volumes that you use in AdvFS domains.
Structuring domains with LSM storage provides some performance and reliability
benefits:
Data mirroring and RAID allow access to the same information
on more than one physical device.
This provides backup in the case of a disk
failure.
Mirroring can improve the I/O throughput because files can
be accessed from more than one physical location.
LSM's volume striping is useful when many files are shared.
AdvFS stripes individual files.
Detailed information on disk I/O activity is available with
LSM monitoring.
You can perform backups without shutdown on a mirrored system
by detaching the mirror, backing up the detached volume, then reattaching
it.
LSM volumes are not backward compatible.
Do not move an LSM volume that
you added to a domain on a Version 5 operating system to a system running
a Version 4 operating system.
See
Logical Storage Manager
for further information.
Use AdvFS commands for AdvFS activities.
To manage LSM storage that
is part of an AdvFS domain, use LSM commands.
If you want to create an LSM
volume or place and existing domain under LSM control, see
Logical Storage Manager.
To use LSM with AdvFS from the command line:
Create the LSM volumes with the desired attributes.
You can specify mirrored volumes, striped volumes, mirrored and striped
volumes, volume location, and volume size.
Create a domain by using the
If desired, and if you have AdvFS Utilities, create a multivolume
domain by using the
See
Logical Storage Manager
for further information.
Do not use the
You will get an error message if you try to create an AdvFS domain on
an LSM volume that is already opened or on a volume that is already labeled
as in use by either UFS or AdvFS.
If you already have an AdvFS domain, you can encapsulate the domain
into LSM by using the LSM encapsulation tools.
If mirrored or striped LSM volumes are part of an AdvFS domain that
also includes non-LSM volumes, you cannot control which files go to the mirrored
or striped LSM volumes.
To place specific data on mirrored or striped volumes,
create an AdvFS domain that contains only LSM volumes that are mirrored or
striped.
Then, migrate the files you want mirrored or striped in that domain.
The
You must use the full LSM pathname when referencing an LSM volume.
The following example creates a domain on an existing LSM volume:
You can also add volumes to an existing domain:
You can configure domains with LSM mirrored volumes.
This configuration
provides failover protection.
Because the multiple copies of the volumes contain
the same information, either one can be accessed.
See
Logical Storage Manager
for detailed instructions
for creating LSM mirrors.
Mirrored volumes are added to AdvFS domains with
AdvFS commands.
You can distribute I/O across multiple volumes by striping.
AdvFS and
LSM striping both work well on a busy system.
LSM is better suited for general
striping, while AdvFS striping allows the administrator finer-grained control
for positioning individual files.
When you choose LSM striping, you configure your LSM volumes for striping
before you add them to the domain.
With LSM striping all files located on
the volumes are striped.
You can do this from the command line or from LSMSA
(see
Logical Storage Manager).
You can perform AdvFS striping at any time (see
Section 4.13).
Therefore, if you find that a file has become large or has heavy I/O requirements,
you can use the AdvFS
It is not advisable to do both LSM and AdvFS striping because this might
degrade system performance.
1.3 File System Design
Figure 1-1: AdvFS File System Design
1.3.1 Filesets, Domains, and Volumes
1.3.2 Transaction log file
fsck
utility to recover from
a system failure.
The
fsck
utility can take hours to check
and repair a large file system.
1.3.3 File Storage Allocation
defragment
utility (see
Section 4.8).
ftruncate
command or by using
the
lseek
and
write
commands to skip over
unwritten sections of the file.
ls -l
command.
The
ls -s
command displays the amount of storage actually used by the
file.
The
du
command provides the same information as the
ls -s
command (see
Section 5.1).
1.4 Setting Up an AdvFS File System
/
(root) and
/usr
file systems on AdvFS.
By using
AdvFS for root and
/usr, you increase configuration flexibility
and significantly reduce system down time in the event of a system failure.
/etc/fstab
file to
automatically mount a fileset at system boot (see
Section 1.7.2).
Alternately, you can use a graphical interface or the SysMan Menu to perform
this activity.
1.5 Volumes
/etc/fdmns
directory (see
Section 1.6.2).
This directory must be up to date; that is, the domain entries must correctly
reference the volumes associated with the domains.
The number of links to
the volumes in the
/etc/fdmns
directory must equal the
number of volumes.
1.5.1 Volume Attributes
chvol
command Manage AdvFS Domains
at any time to change the attributes of a volume in an active domain; the
system does not have to be quiescent.
chvol
command from
the command line:
chvol
device_name file_domain
1.6 Domains
/etc/fdmns
directory.
This entry contains the links to the volumes that comprise
the domain.
1.6.1 Configuring Domains
g
to one
domain and partition
h
of the same disk to another domain.
c) to a domain is preferable to adding several
partitions on the same disk.
Adding several partitions might degrade performance.
An error message is displayed if you try to assign overlapping partitions
to a domain (see
Section 1.6.6).
defragment
utility processes each volume
in parallel.
1.6.2 The /etc/fdmns Directory
/etc/fdmns directory
defines domains by providing
a subdirectory for each domain you create.
The subdirectories contain a symbolic
link to every volume in the domain.
/etc/fdmns
directory in order to mount the filesets in a domain.
/etc/fdmns
directory to the block device.
You cannot
create a domain by creating a link in the directory.
/etc/fdmns
directory regularly.
If the
contents of the directory become corrupt or if the directory is deleted, restore
the directory from your most recent backup.
A damaged directory prevents access
to the domain because the information matching the domain to the physical
volume containing the filesets is incorrect; the filesets are not affected.
accounts
is displayed:
Volume count mismatch for domain accounts.
accounts expects 2 volumes, /etc/fdmns/accounts has 1 links.
/etc/fdmns
directory is damaged or if the
volumes of a domain are moved to a different system, use the
advscan
utility to locate the volumes and reconstruct the directory (see
Section 5.9).
1.6.3 Version 5.0 Domains
1.6.3.1 Creating a Domain with DVN4
/root,
/usr, and
/var
also
have a DVN of 3.
There is no conversion utility.
To move your data to a DVN4
domain, back up your data, create a new DVN4 domain, and restore it to the
new domain.
1.6.3.2 Upgrading a Domain to DVN4
showfile
command
to determine if a directory is indexed.
Use the
-i
option
to display information about the index.
See
showfile(8)
for more information.
vdump
command.
It is a good idea to use the
-x
option for additional protection from saveset errors.
You lose all the data
in your domain if you cannot restore it after creating a new domain.
rmfdmn
command.
mkfdmn
command.
The new domain has a DVN of 4.
You do not need to use the
-x
and
-p
options for the
mkfdmn
command.
DVN4 domains do not require additional of BMT allocations.
mkfset
command.
vrestore
command.
domain_p
on
/dev/disk/dsk1c
containing filesets
fset_p
and
fset_m
and put them back on the same volume with the same names,
enter the following commands:
# vdump -0 -N -x 8 /fset_p
# vdump -0 -N -x 8 /fset_m
# umount /fset_p
# umount /fset_m
# rmfdmn domain_p
# mkfdmn /dev/disk/dsk1c domain_p
# mkfset domain_p fset_p
# mkfset domain_p fset_m
# mount domain_p#fset_p /fset_p
# mount domain_p#fset_m /fset_m
# vrestore -x -D /fset_p
# mt fsf 1
# vrestore -x -D /fset_m
mkfdmn(8)
for more information.
1.6.4 Displaying Domain Information
showfdmn
command:
showfdmn
domain_name
domain_1
domain:
# showfdmn domain_1
Id Date Created LogPgs Version Domain Name
2bb0c594.00008570 Fri Mar 24 12:33 2000 512 4 domain_1
Vol 512-Blks Free % Used Cmode Rblks Wblks Vol Name
1L 8325 79210 90% on 128 128 /dev/disk/dsk1c
2 832527 1684 98% on 128 128 /dev/disk/dsk2c
-------------------------
1665054 80894 94%
Figure 1-2: Single-Volume Domain
mkfdmn
command from the command
line:
mkfdmn
volume_name domain_name
mkfdmn
command.
mkfset
command.
mkdir
command.
It is convention to name the directory the same as the
fileset.
For example, if the fileset is
tmp, name the mount-point
directory
/tmp.
mount
command.
mkfdmn(8).
Caution
mkfdmn
command on a volume containing
data that you want to keep.
Doing so destroys the data.
If you have accidentally
used the
mkfdmn
command, you might recover some of your
data by using the
salvage
utility if the volume is an AdvFS
volume (see
Section 5.8.4).
domain_2, and two filesets,
fset_a
and
fset_b, in the domain.
Because the domain has only one volume, the
files in both filesets physically reside on one volume.
This is allowed in
AdvFS.
The number sign (#) between the domain and fileset names is part of
the naming syntax and does not represent a comment.
# mkfdmn /dev/disk/dsk2c domain_2
# mkfset domain_2 fset_a
# mkfset domain_2 fset_b
# mkdir /fset_a
# mkdir /fset_b
# mount domain_2#fset_a /fset_a
# mount domain_2#fset_b /fset_b
mkfdmn
command fails if
the volume is mounted or if it is a current swap partition.
If the volume
is unmounted, you get an warning message.
You can override the message and
create the domain.
For example, if
/dev/disk/dsk3g
is in
use and you try to create the domain
usr_domain, the following
message is displayed:
# mkfdmn /dev/disk/dsk3g usr_domain
Warning: /dev/rdisk/dsk3g is marked in use for 4.2BSD.
If you continue with the operation you can
possibly destroy existing data.
CONTINUE? [y/n] <y>
1.6.6 Increasing the Size of a Domain
Figure 1-3: Enlarging a Domain
Caution
grow
option to increase its size.
addvol
command from the command line:
addvol device_name domain_name
dsk3c
to the domain
resources:
#
addvol /dev/disk/dsk3c
resources
Caution
addvol
command to add a volume containing
data that you want to keep.
Doing so destroys the data.
If you have accidentally
used the
addvol
command, you might recover some of your
data by using the
salvage
utility (see
Section 5.8.4).
vdump/vrestore, cpio,
cp -R, or tar) to copy each fileset from the old device to the newly
mounted fileset.
/etc/fstab
file.
If you do change the names, change them in the
/etc/fstab
file.
showfdmn
command to
display the contents of the domain and the current disk capacity of each volume.
balance
utility to
even the file distribution between the volumes.
/dev/disk/dsk2c, of the
domain_1
domain with
a larger disk, the volume
/dev/disk/dsk3c:
# showfdmn domain_1
Id Date Created LogPgs Version Domain Name
2bb0c594.00008570 Fri Mar 24 12:33 2000 512 4 domain_1
Vol 512-Blks Free % Used Cmode Rblks Wblks Vol Name
1L 832527 79210 90% on 128 128 /dev/disk/dsk1c
2 832527 1684 98% on 128 128 /dev/disk/dsk2c
-------------------------
1665054 80894 94%
# addvol /dev/disk/dsk3c domain_1
# rmvol /dev/disk/dsk2c domain_1
# balance domain_1
addvol -F
command.
Caution
addvol(8)).
1.6.7 Reducing the Size of a Domain
Caution
shrink
option to reduce its size.
rmvol
command from the command line:
rmvol
device_name domain_name
dsk3c
from the domain
inventory:
#
rmvol /dev/disk/dsk3c
inventory
rmvol
process (see
rmvol(8))
with Ctrl/c or by using the
kill -term
command without
damaging your domain.
Files already removed remain in their new location.
Do not use the
kill -KILL
command.
rmvol
command
by using the
kill
command can leave the volume in an inaccessible
state; that is, it cannot be written to.
Volumes in this condition are marked
as "data unavailable" in the output of the
showfdmn
command.
If a volume does not allow writes after an aborted
rmvol
operation, use the
chvol -A
command to reactivate
the volume.
showfdmn
command to display the
contents of the domain and the current disk capacity of each volume.
This
step is optional.
balance
utility to even the file
distribution between the remaining volumes.
This step is not required.
domain_2
domain,
/dev/disk/dsk2c:
# showfdmn domain_2
Id Date Created LogPgs Version Domain Name
2bb0c594.00008570 Fri Jun 9 10:23 2000 512 4 domain_2
Vol 512-Blks Free % Used Cmode Rblks Wblks Vol Name
1L 832527 386984 54% on 128 128 /dev/disk/dsk1c
2 832527 647681 22% on 128 128 /dev/disk/dsk2c
3 832527 568894 32% on 128 128 /dev/disk/dsk3c
----------------------
249758 1603559 36%
# rmvol /dev/disk/dsk2c domain_2
# balance domain_2
rmvol
utility moves the segment to another volume that does not
already contain a stripe segment of the same file.
When a file is striped
across all volumes in the domain, a confirmation is required before removing
the volume.
If you allow the removal process to continue, more than one stripe
segment is placed on the remaining volumes.
See
Section 4.13
for details on file striping.
1.6.8 Removing a Domain
/etc/fdmns
directory
that defined the domain is removed and you cannot mount the filesets.
Volumes
that were assigned to the removed domains are relabeled as unused and can
be reused.
rmfset
command to remove each fileset might present a security hole
because no data on the volumes is changed.
You might be able to access your
data by using the
salvage
command (see
Section 5.8.4).
rmfdmn
command:
rmfdmn
domain_name
promotions:
# rmfdmn promotions
rmfdmn: remove domain promotions? [y/n]y
rmfdmn: domain promotions removed
1.6.9 Renaming a Domain
/etc/fstab
file (see
Section 1.7.2).
To rename a domain, use a graphical user interface (see
Appendix D)
or, from the command line:
/etc/fdmns
directory, change the
old domain name to the new one:
#mv /etc/fdmns/old_dom_name /etc/fdmns/new_dom_name
/etc/fstab
file to enter the new
domain name and remove the old.
marketing
to
advertising, assuming one fileset,
fset, is mounted
at
/fset
using the vi editor:
# umount /fset
# mv /etc/fdmns/marketing /etc/fdmns/advertising
# vi /etc/fstab
/etc/fstab
file:
marketing#fset /fset advfs rw,userquota,groupquota 0 2
advertising#fset /fset advfs rw,userquota,groupquota 0 2
# mount /fset
domain#fileset.
Here the number sign (#) is part
of the naming syntax and does not represent a comment.
1.7.1 Configuring Filesets
vdump
or
vrestore
commands on several filesets simultaneously.
1.7.2 Designating Filesets in the /etc/fstab File
/etc/fstab
file by listing
them with an
advfs
designation (see
fstab(4)).
This is similar
to the way that you add any other file system.
AdvFS filesets listed in the
/etc/fstab
file are mounted each time you reboot the system.
userquota
and
groupquota
options (see
Section 2.2) and the pass field numbers:
file_dmn#fileset /mount_point advfs rw,userquota,groupquota 0 2
credit
fileset
(assuming the fileset's mount point exists), add the following line to the
/etc/fstab
file:
acct_domain#credit /credit advfs rw,userquota,groupquota 0 2
userquota
and
groupquota
options
identify the mounted file systems that can be processed by quota-related commands.
Many quota commands have a
-a
(all) option that directs
the command to operate only on file systems specified in this way.
1.7.3 Displaying Fileset Information
showfsets
domain_name
big_domain,
which has four filesets:
# showfsets big_domain
staff1_fs
Id : 2cb9d009.000419f4.1.8001
Files : 18554, SLim= 0, HLim= 0
Blocks(512) : 712230, SLim= 0, HLim= 0
Quota Status : user=on group=on
Object Safety: off
Fragging : on
DMAPI : off
guest_fs
Id : 2cb9d009.000419f4.2.8001
Files : 4765, SLim= 0, HLim= 0
Blocks(512) : 388698, SLim= 0, HLim= 0
Quota Status : user=on group=on
Object Safety: off
Fragging : on
DMAPI : off
staff2_fs
Id : 2cb9d009.000419f4.3.8001
Files : 12987, SLim= 0, HLim= 0
Blocks(512) : 842862, SLim= 0, HLim= 0
Quota Status : user=on group=on
Object Safety: off
Fragging: on
DMAPI : off
staff3_fs
Id : 2cb9d009.000419f4.4.8001
Files : 48202, SLim= 0, HLim= 0
Blocks(512) : 1341436, SLim= 0, HLim= 0
Quota Status : user=on group=on
Object Safety: off
Fragging : on
DMAPI : off
domain_2, which contains
one fileset and one fileset clone:
# showfsets domain_2
test_fs
Id : 3003f44f.0008ac95.4.8001
Clone is : clone_test
Files : 7456, SLim= 0, HLim= 0
Blocks (512) : 388698, SLim= 0, HLim= 0
Quota Status : user=on group=on
Object Safety: off
Fragging : on
DMAPI : off
Clone_test
Id : 3003f44f.0008ac95.5.8001
Clone of : test_fs
Revision : 2
1.7.4 Creating a Fileset
mkfset
command or change them
by using the
chfsets
command (see
Section 1.7.10).
mkfset
command from the command line:
mkfset
domain_name fileset_name
coupons
in the
domain
advertising:
# mkfset advertising coupons
1.7.5 Upgrading a Fileset
1.7.6 Mounting a Fileset
mount
command from the command line:
mount
domain_name#fileset_name
mnt_point
coupons
in the domain
advertising:
# mkdir /coupons
# mount advertising#coupons /coupons
advscan(8)
for further information.
1.7.7 Unmounting a Fileset
umount
command from the command line:
umount
mnt_point
coupons
in the
domain
advertising
that was mounted in
Section 1.7.6:
#
umount /coupons
1.7.8 Removing a Fileset
rmfset
command:
rmfset
domain_name fileset_name
tmp_1
fileset in
domain_1:
# rmfset domain_1 tmp_1
rmfset: remove fileset tmp_1? [Y/N]y
rmfdmn
command.
However, you might be able to access
some of the data by using the
salvage
utility (see
Section 5.8.4).
The
rmfdmn
command
removes the definition of the domain in the
/etc/fdmns
directory and relabels the volumes, but it does not touch any data on the
volume.
If you remove filesets by using the
rmfset
command,
you cannot recover them by using the
salvage
utility because
the utility destroys pointers to the metadata for all the files in the fileset.
1.7.9 Renaming a Fileset
renamefset
domain_name old_fileset_name
new_fileset_name
/etc/fstab
file (see
Section 1.7.2).
If you do not do this, AdvFS does not mount the fileset when the system is
booted.
sad
fileset that is mounted
at
/mntpt
to
happy
using the vi editor:
# umount /mntpt
# renamefset dmn_1 sad happy
# vi /etc/fstab
/etc/fstab
file:
dmn_1#sad /mntpt advfs rw,userquota,groupquota 0 2
dmn_1#happy /mntpt advfs rw,userquota,groupquota 0 2
# mount /mntpt
Note
1.7.10 Changing the Characteristics of a Fileset
chfsets
command you can change the quota
limits for a fileset by using the
-F,
-f,
-B, and
-b
options (see
Section 2.2.2)
and by using the
-o
option you can turn fragment files
on and off (see
Section 4.2), and enable or disable object safety.
From
chfsets
command has the following syntax:
chfsets
[-F limit] [-f limit] [-B
limit] [-b limit] [-o <frag|nofrag>
<objectsafety|noobjectsafety>
<dmapi|nodmapi>]
domain_name [fileset_name]
xyz3
fileset in the
xyz_domain:
# chfsets -o objectsafety xyz_domain xyz3
1.7.11 AdvFS Fileset Clones
vdump
command, for example).
However, it can provide internal consistency
if you are trying to back up a system where files are changing rapidly and
you want to retain the information at a particular time.
Use the clone to
make a snapshot of your data, then use the
vdump
command
to back up the clone.
Note
df
command,
which displays statistics on free disk space, does not accurately reflect
the size of the fileset clone because it constantly changes as files are updated.
Caution
1.7.11.1 Creating an AdvFS Fileset Clone
clonefset
command from the command line:
clonefset
domain_name fileset_name
clone_name
clone_day300
for the fileset
day300
in the domain
transactions:
#
clonefset transactions
day300 clone_day300
1.7.11.2 Mounting and Unmounting an AdvFS Fileset Clone
1.7.11.3 Removing an AdvFS Fileset Clone
1.7.11.4 Renaming an AdvFS Fileset Clone
1.8 Setting Up Trashcans
mv
command.
rmfset
command,
the files in it are not saved.
Table 1-1: Trashcan Commands
Command
Description
mktrashcanCreates the trashcan
shtrashcan
Shows the contents of the trashcan
rmtrashcan
Removes the trashcan directory
keeper
to the directory
booklist:
# mkdir keeper
# mktrashcan keeper /booklist
'keeper' attached to '/booklist'
# rm old_titles
# shtrashcan /booklist
'//keeper' attached to '/booklist'
# cd keeper
# ls
old_titles
# rmtrashcan /booklist
'/booklist' detached
1.9 Configuring an AdvFS root File System
fsck
utility after a crash.
addvol
and
rmvol
commands are available to manage the root file system, except in
a cluster configuration where multivolume root domains are allowed.
a
or
c
partitions).
/etc/fstab
file.
/usr
and
/var
filesets
in the root domain.
If you have only one storage device on your system, put
other domains on different partitions.
a
partition.
a
or
c
partition.
See
Section C.2
for instructions on converting an existing UFS root file system to AdvFS.
See the
Installation Guide
for instructions on installing
AdvFS as the root file system during the initial installation.
1.9.1 Mounting the root File System in Single-User Mode
mount -u
command:
#
mount -u /
/etc/fstab
file.
1.9.2 Changing the Name of the root Domain
/etc/fdmns
directory and in the entry
for root in the
/etc/fstab
file.
1.9.3 Changing the Name of the root Fileset
renamefset
command requires that the
fileset be unmounted, and you cannot unmount the root fileset.
/etc/fstab
file to change
the name of the root fileset.
To do this, you must make the root fileset writable.
But you cannot mount the root fileset as writable unless the
/etc/fstab
entry is correct.
/etc/fdmns
directory
of the booted partition for the fileset whose name you want to change.
renamefset
command to rename the
root fileset.
/etc/fstab
file.
fstab
entry to correspond to
the new root fileset name.
root_fs
to
new_root.
Assume that the root fileset
is in the
root_domain
domain on
/dev/disk/dsk2a.
tmp_root_domain
in the
/etc/fdmns
directory:
#mkdir /etc/fdmns/tmp_root_domain
tmp_root_domain:
# cd /etc/fdmns/tmp_root_domain
# ln -s /dev/disk/dsk2a
root_fs
to
new_root:
# renamefset tmp_root_domain root_fs new_root
/etc/fstab
file:
#mount tmp_root_domain#new_root /mnt
/mnt/etc/fstab
entry for
tmp_root_domain
using the vi editor:
# cd /mnt/etc
# vi fstab
/etc/fstab
file:
root_domain#root_fs / advfs rw,userquota,groupquota 0 2
root_domain#new_root / advfs rw,userquota,groupquota 0 2
# shutdown -h now
Note
/etc/fstab
entries, you cannot boot past single-user mode.
Edit
/etc/fstab
file in single-user mode using an editor to proceed.
Caution
1.10.1 Setting Up AdvFS Using LSM Volumes
mkfdmn
command
and identify the LSM volume as the initial volume.
addvol
command adding either LSM or
non-LSM volumes.
Caution
grow
or
shrink
LSM options to change the size of AdvFS domains.
Use the
addvol
and
rmvol
commands instead.
showfdmn
command output, the LSM Storage Administrator
(LSMSA), and the AdvFS GUI (see
Appendix D) include LSM storage
in the domain information display.
Note
#
mkfdmn /dev/vol/rootdg/vol01
domain_rs
#
addvol /dev/vol/rootdg/vol02
domain_rs
1.10.2 Using LSM for Data Redundancy
1.10.3 Striping LSM Volumes and Striping AdvFS Files
stripe
command to stripe it.