pfs_mount(1M)
NAME
pfs_mount, pfs_umount − mount and unmount CD-ROM file systems
SYNOPSIS
pfs_mount
pfs_mount [−v −f −n] [ −t type ] [ −x xlat ] [ −o options ] filesystem directory
pfs_mount [−v −f −n] [ −x xlat ] [ −o options ] filesystem | directory
pfs_umount [ −v ] filesystem | directory
DESCRIPTION
pfs_mount attaches a named filesystem to the file system hierarchy at the pathname location directory, which must already exist. If directory has any contents prior to the mount operation, these remain hidden until the filesystem is once again unmounted. If filesystem is of the form host:pathname , it is assumed to be a remote file system.
In the case of a local mount, pfs_mount probes the specified device to determine the file system type. It then contacts the local mountd to register the specified directory as a valid mounted file system. pfs_mountd.rpc will reply with the address of the pfsd.rpc who will be handling all requests for files on that directory.
Remote mounts are very similar, except that both the local and remote mount daemons will be contacted. The remote mount daemon will supply the pfs server address, and the local mount daemon will be contacted to register the mount.
pfs_umount unmounts a currently mounted file system, which can be specified as a either directory or a filesystem.
pfs_umount contacts the local mount daemon to determine what actions should be taken to perform the unmount. If the file system was originally remotely mounted, the remote mount daemon is informed of the unmount, and the file system is unmounted. Otherwise, it is simply unmounted.
pfs_mount and pfs_umount maintain a table of mounted file systems in /etc/mtab, described in pfs_fstab(5). If invoked without an argument, pfs_mount displays the contents of this table. If invoked with either a filesystem or a directory only, mount searches the file /etc/pfs_fstab for a matching entry, and mounts the file system indicated in that entry on the indicated directory.
pfs_mount Options
−v Verbose. Display a message indicating each file system being mounted.
−f Fake an /etc/mtab entry, but do not actually mount any file systems.
−n Mount the file system without making an entry in /etc/mtab.
−x xlat Filename translation options. Any combination can be specified, although some combinations do not make sense (i.e. dot_version and no_version).
no_version will suppress the printing of the version number (and semicolon) at the end of iso9660 and high sierra filenames.
dot_version replaces the version number (and semicolon) with a period followed by the version number.
lower_case Converts upper to lower case on all file (and directory) names. version number.
unix Shorthand for no_version and lower_case
−t type Force the CD-ROM to be mounted as the specified type, if possible. Accepted types are:
iso9660 will cause the mount program to attempt to mount the CD-ROM image using the iso9660 specifications. If the CD image is not iso9660 compatible, the mount fails. Note that if the CD image is also RockRidge compliant, and the -t iso9660 option is not specified, the CD-ROM image will be mounted with RockRidge extensions enabled.
hsfs will cause the mount program to attempt to mount the CD-ROM image using the high sierra specifications. If the CD image is not hsfs compatible, the mount fails.
rrip will cause the mount program to attempt to mount the CD-ROM image using the RockRidge Interchange specifications. If the CD image is not rrip compatible, the mount fails. Note, that if the CR-ROM image is supports the RockRidge Interchange Protocol, and the CR-ROM image is mounted with rrip, the translation options are suppressed.
Note that these get entered into the /etc/mtab and /etc/pfs_fstab with a pfs- preceding the type. This is to avoid confusing other programs which may scan the /etc/mtab looking for types of the same name.
−o options Specify file system options as a list of comma-separated words from the list below.
options valid on all file systems:
ro Even if not specified, the read-only option is implied.
suid|nosuid Setuid execution allowed or disallowed.
bg|fg If the first attempt fails, retry in the background, or, in the foreground.
retry=n The number of times to retry the mount operation.
rsize=n Set the read buffer size to n bytes.
timeo=n Set the PFS timeout to n tenths of a second.
retrans=n The number of PFS retransmissions.
soft|hard Return an error if the server does not respond, or continue the retry request until the server responds.
intr Allow keyboard interrupts on hard mounts.
The defaults are:
suid,fg,retry=10000,timeo=7,rsize=2048,retrans=3,hard,\
acsize=1037,bcsize=100,lcsize=500
options specific to iso9660 and hsfs file systems:
xlat=xlat_flags xlat_flags is a colon (:) separated list of translation options. Currently supported are no_version, dot_version, lower_case, and unix. They allow you to perform the same translations options the -x flag does. The -x flag remains for backward compatibility. It is suggested that you use the xlat= option flag as they can be placed in the pfs_fstab file.
pfs_umount Options
−v Verbose. Display a message indicating each file system as it is unmounted.
Background vs. Foreground
Filesystems mounted with the bg option indicate that mount is to retry in the background if the server’s mount daemon (pfs_mountd(1M)) does not respond. mount retries the request up to the count specified in the retry=n option. Once the file system is mounted, each PFS request made in the kernel waits timeo=n tenths of a second for a response. If no response arrives, the time-out is multiplied by 2 and the request is retransmitted. When the number of retransmissions has reached the number specified in the retrans=n option, a file system mounted with the soft option returns an error on the request; one mounted with the hard option prints a warning message and continues to retry the request.
Interrupting Processes With Pending PFS Requests
The intr option allows keyboard interrupts to kill a process that is hung while waiting for a response on a hard-mounted file system.
Attributes Cache
The server’s attribute cache retains file attribute information on requests that have been made. This provides faster access to entries which have previously been decoded.
Lookup Cache
The LookupCache holds information about the sequential nature of the directory entries. This cache stores the location of the next directory entry. When a request comes in for a directory entry, if the preceding directory entry had been accessed earlier, this location is examined first to see if the directory entry being requested matches the directory entry at that location.
Block Cache
This cache holds raw 8k blocks of recently accessed data.
EXAMPLES
To mount a CD-ROM disk:
pfs_mount /dev/sr0 /cd-rom
To mount a remote file system:
pfs_mount serv:/cd-rom /cd-rom
To fake an entry for iso9660 on /cd-rom:
pfs_mount −f -t iso9660 /dev/sr0 /cd-rom
To hard mount a remote file system:
pfs_mount −o hard serv:/cd-rom /cd-rom
AUTHOR
pfs_mount was developed by Young Minds, Inc.
FILES
/etc/mtab table of mounted file systems
/etc/pfs_fstab table of pfs file systems
SEE ALSO
fstab (5), mtab (5), pfs_fstab (5), pfs_mountd (1M), pfsd (1M).
BUGS
If the directory on which a file system is to be mounted is a symbolic link, the file system is mounted on the directory to which the symbolic link refers, rather than being mounted on top of the symbolic link itself.
On pioneer six disc changers (and perhaps other drives) if you mount the file system using the block device driver (/dev/sr0 for Sun), the pioneer returns information to the driver indicating there is no data, causing the mount to fail. Either mount the file system again (which will should succeed), or use the raw device driver (/dev/rsr0 for Sun).
Hewlett-Packard Company — HP-UX Release 10.20: July 1996