|
|
HP-UX Reference > Ppfs_mount(1M)OBSOLETEDHP-UX 11i Version 2: December 2007 Update |
|
NAMEpfs_mount, pfs_umount — mount and unmount CD-ROM file systems SYNOPSISpfs_mount [-v -a] pfs_mount [-v -a -f -n] [ -t type ] [ -x xlat ] [ -o options ] filesystem directory pfs_mount [-v -a -f -n] [ -x xlat ] [ -o options ] filesystem | directory pfs_umount [ -v -a -c ] filesystem | directory DESCRIPTIONpfs_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 pfs_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 character device to determine the file system type. It then contacts the local pfs_mountd.rpc program 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 PFS file system, which can be specified as either a 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/pfs_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, pfs_mount searches the file /etc/pfs_fstab for a matching entry, and mounts the file system indicated in that entry on the indicated directory. If a user unmounts a PFS file system with the umount program, or interrupts the pfs_umount program before it has completed processing, the PFS daemons may leave the mount device open after the file system is no longer accessible. To clear these problems, use the -c flag for pfs_umount. PFS expects a character device to be used for mounts, not a block device. Use of a block device with PFS is not supported. pfs_mount Options
pfs_umount Options
pfs_mount CONFIGURATIONSBackground vs. ForegroundFilesystems mounted with the bg option indicate that pfs_mount is to retry in the background if the server's mount daemon (see pfs_mountd(1M)) does not respond. pfs_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 RequestsThe intr option allows keyboard interrupts to kill a process that is hung while waiting for a response on a hard-mounted file system. Attributes CacheThe 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 CacheThe Lookup Cache 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. EXAMPLESTo mount a CD-ROM disk: pfs_mount /dev/rdsk/c0t6d0 /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/rdsk/c0t6d0 /cd-rom To hard mount a remote file system: pfs_mount -o hard serv:/cd-rom /cd-rom WARNINGSPFS is obsolete and no longer supported on any HP-UX release. Delivery of PFS interfaces will be discontinued in the next HP-UX release. PFS, from Young Minds, Inc. (now defunct), was originally adopted by HP to provide accessibility to Rock Ridge Interchange file system format on CD-ROM file systems. The equivalent functionality is now provided via the HP-UX CDFS file system type and HP-UX's standard file systems commands. PFS has known functionality and performance problems. HP customers are urged to stop using the PFS interfaces, including these interfaces, pfs_mount and pfs_umount. Customers should move to accessing all CD-ROM file system formats by using the standard HP-UX commands, specifying the file system type as cdfs. For example, to mount a CD-ROM file system, use: mount -F cdfs /dev/dsk/c0t0d4 /cdrom There is no need to treat the cdfs file system type differently from any other file system type, therefore no special daemons or commands are required to access the variety of CD-ROM file system formats. See mount(1M) and mount_cdfs(1M). BugsIf 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, 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. |
|