Softpanorama (slightly skeptical) Open Source Software Educational Society

May the source be with you, but remember the KISS principle ;-)

Solaris Mount  Tutorial

mounting is a process that attach individual file systems to their mount points on the directory hierarchy. This action makes a file system accessible to the system and to the users.

You use the unmounting process to detach a file system from its mount point in the directory hierarchy. This action makes a file system unavailable to the system or users.

After you have created a file system by using the newfs command, you must attach it to the Solaris OE directory hierarchy at a mount point. A mount point is a directory that is the point of connection for a file system.  File systems are commonly referred to by the names of their mount points, for example, the / (root) file system or the /usr file system.

To determine which file systems are currently mounted use

• mount command. The mount command, which is located in the /usr/sbin directory, maintains a table of currently mounted file systems in the /etc/mnttab file. When the mount command is used without arguments, it lists all of the mounted file systems in the /etc/mnttab directory. When used with only a partial argument list, the command searches the /etc/vfstab file for an entry that supplies the missing arguments.

• df command. The df command displays the amount of disk space occupied by mounted or unmounted file systems and, depending on the options used, displays both locally mounted and virtual file system information.

Note – While system administrators typically use the /usr/sbin/mount command, the system boot scripts use the /sbin/mount command.

The Solaris OE provides several methods for automating file system mounts.

• The Solaris OE creates a default /etc/vfstab file during software installation, based on your selections. However, you can edit the /etc/vfstab file whenever file system entries need to be added or modified.

• The automounter can mount network file systems on demand.

/etc/vfstab Virtual File System Table

The /etc/vfstab file lists all the file systems to be automatically mounted at system boot time, with the exception of the /etc/mnttab and /var/run file systems.

The file format includes seven fields per line entry. By default, a tab separates each field, but any whitespace can be used for separators. The dash (-) character is used as a placeholder for fields when text arguments are not appropriate. Commented lines begin with the hash (#) symbol.

To add a line entry, you need the following information:

Note – For / (root), /usr, and /var (if it is a separate file system) file systems, the mount at boot field value is specified as no. The kernel mounts these file systems as part of the boot sequence before the mountall command is run. The mount command explicitly mounts the file systems / (root) and /usr as specified in the /etc/rcS.d/S30rootusr.sh script and the /var file system as specified in the /etc/rcS.d/S70buildmnttab script.

• device to mount The device to be mounted. For example, a local ufs file system /dev/dsk/c#t#d#s#, or a pseudo file system /proc.

• device to fsck The raw or character device checked by the file system check program (fsck) if applicable. A pseudo file system has a dash (-) in this field.

• mount point The name of the directory that serves as the attach mount point in the Solaris OE directory hierarchy.

• FS type The type of file system to be mounted.

• fsck pass Indicates whether the file system is to be checked by the fsck utility at boot time. A 0 (zero) or a nonnumeric in this field indicates no. A 1 in this field indicates the fsck utility gets started for that entry and runs to completion. A number greater than 1 indicates that the device is added to the list of devices to have the fsck utility run. The fsck utility can run on up to eight devices in parallel. This field is ignored by the mountall command.

• mount at boot Enter yes to enable the mountall command to mount the file systems at boot time. Enter no to prevent a file system mount at boot time.

• mount options A comma-separated list of options passed to the mount command. A dash (-) indicates the use of default mount options.

Note – Because the default is to use tabs to separate the fields in the /etc/vfstab file, the fields often do not line up under their respective headings. This can lead to some confusion when you are viewing this file in a terminal window.

An example of a /etc/vfstab file follows:

/etc/mnttab file system that provides read-only information directly from the kernel

The /etc/mnttab file is really an mntfs file system that provides read-only information directly from the kernel about mounted file systems on the local host.

Each time a file system is mounted, the mount command adds an entry to this file. Whenever a file system is unmounted, its entry is removed from the /etc/mnttab file.

• Mount Point The mount point or directory name where the file system is to be attached within the / (root) file system (for example, /usr, /opt).

• Device Name The name of the device that is mounted at the mount point. This block device is where the file system is physically located.

• Mount Options The list of mount options in effect for the file system. dev=number The major and minor device number of the mounted file system.

• Date and Time Mounted The date and time that the file system was mounted to the directory hierarchy.

• The /var/run file system is a tmpfs mounted file system in the Solaris OE. It is the repository for temporary operating system files that are not needed across system reboots in this Solaris OE release. It is mounted as a pseudo file system rather than a disk-based file system.

• The /var/run directory requires no administration. For security reasons, it is owned by the root user.

• The /tmp directory continues to be a tmpfs mounted file system in the Solaris OE. It is the repository for temporary user and application files that are not needed across system reboots. It is a pseudo file system rather than a disk-based file system.

The following examples show two ways to display currently mounted file systems.

You can mount file systems manually by logging in as the root user and running the mount command, or the system can automatically mount file systems at boot time after consulting the /etc/vfstab file.

The mount command not only lists which file systems are currently mounted, it also provides you, as the root user, with a method for mounting file systems.

To mount a local file system manually, you need to know the name of the device where the file system resides and its mount point directory name. Perform the command:

# mount /dev/dsk/c0t0d0s7 /export/home

In this example, the default action mounts the file system with the following options: read/write, setuid, intr, nologging, and largefiles, xattr, and onerror.

The following list explains the default options for the mount command.

• read/write Indicates whether reads and writes are allowed on the file system.

• setuid Permits the execution of setuid programs in the file system.

• intr/nointr Allows and forbids keyboard interrupts to kill a process that is waiting for an operation on a locked file system.

• nologging Indicates that logging is not enabled for the ufs file system.

• largefiles Allows for the creation of files larger than 2 Gbytes.A file system mounted with this option can contain files larger than 2 Gbytes.

• xattr Supports extended attributes not found in standard UNIX attributes.

Note – Due to file system overhead, the largest file size that can be created is approximately 866 Gbytes.

The /etc/vfstab file provides you with another important feature. Because the /etc/vfstab file contains the mapping between the mount point and the actual device name, the root user can manually mount a file system specifying only the mount point on the command line.

# mount /export/home  # means take options from /etc/vfstab

Using the mount Command Options

mount command is unique amont Unix utilities in that it requres options to be preseded by the -o flag. When you are using multiple options, enter them as a comma-separated list following the -o flag. Some options used to mount local file systems include: ro, nosetuid,

mount -o option,option,... device_name mount_point

Note – Mount options are discussed in detail in the man page for the mount_ufs command.

• onerror=action Specifies the action that the ufs file system should take to recover from an internal inconsistency on a file system. An action can be specified as:

  • panic—Causes a forced system shutdown. This is the default.

  • lock — Applies a file system lock to the file system.

  • umount — Forcibly unmounts the file system.

• noatime, nolargefiles, and logging.

• l ro – Mounts the file system as read-only.The following is an example using this option on the command line:

# mount -o ro /dev/dsk/c0t0d0s6 /usr

• l nosuid – Prohibits the execution of setuid programs in the filtsystem. This does not restrict the creation of setuid programs.The following example shows the use of multiple options on the command line:

# mount -o ro,nosuid /dev/dsk/c0t0d0s7 /export/home

• l noatime – Suppresses the time-last-accessed modification on inodes, which reduces disk activity on a file system where access times are not important. Specifying this option generally improves file access times and boosts overall performance, for example:

# mount -o noatime /dev/dsk/c0t0d0s7 /export/home

• l nolargefiles – Prevents a file system that contains one or more "large files" from being mounted, for example:

# mount -o nolargefiles /dev/dsk/c0t0d0s7 /export/home

Use of the nolargefiles option fails if the file system to be mounted contains a large file or did contain a large file at one time. If the file system currently contains a large file and the root user needs to mount it with this option, then the large file must be located and moved or removed from the file system. Then you must execute the fsck command manually to update the superblock information. The mount also fails if the file system at one time contained a large file, even though it was moved or removed. You must execute the fsck command to clear the old information and allow the file system to be mounted.

• l logging – Enables logging for a ufs file system, for example:

# mount -o logging /dev/dsk/c0t0d0s7 /export/home

UFS logging is a process of storing file system transactions or changes that make up a complete file or directory operation into a log before they are applied to the file system. After a transaction is stored, the complete transaction can be applied to the file system later. The UFS log is allocated from free blocks in the file system. It is sized approximately 1 Mbyte per 1 Gbyte, up to a maximum of 64 Mbytes.

As a UFS log reaches its maximum size, it begins to write transactions to the file system. When the file system is unmounted, the entire UFS log is emptied, and all transactions are written to the file system. UFS logging offers two advantages. First, it prevents file systems from becoming inconsistent, therefore eliminating the need to run lengthy fsck scans. Secondly, you can bypass fsck scanning, which reduces the time required to reboot a system if it was stopped by a method other than an orderly shutdown.

The /etc/vfstab file is read by the /usr/sbin/mountall command during the system boot sequence and mounts all file systems that have a yes in the mount at boot field. The root user can use the mountall command to mount manually every file system in the /etc/vfstab file that has a yes in the mount at boot field, for example:

    # mountall

To mount only the local file systems listed in the /etc/vfstab file, execute:

# mountall -l

During the boot sequence, the fsck utility checks each local file system in the /etc/vfstab file that has a device to fsck entry and an fsck pass number greater than 0. The utility determines if the file system is in a usable state to be safely mounted.

If the fsck utility determines that the file system is in an unusable state (for example, corrupted), the fsck utility repairs it before the mount is attempted. The system attempts to mount any local file systems that have a - (dash) or 0 (zero) entry in the fsck pass field without checking the file system itself.

To add a new disk to the system, prepare the disk to hold a file system, and mount the file system, perform these general steps:

1. Set up the disk hardware, which might include setting address switches and connecting cables.

2. Perform a reconfiguration boot or run the devfsadm utility to add support for the new disk.

3. Use the format utility to partition the disk into one or more slices.

4. Create a new file system on one slice by using the newfs command.

5. Create a mount point for the file system by using the mkdir command to create a new directory in the / (root) file system.
       # mkdir /database

6. Mount the new file system manually by using the mount command.

# mount /dev/dsk/c1t4d0s0 /database

7. Use the mount command to determine if the file system is mounted.

# mount

8. Edit the /etc/vfstab file to add a line entry for the new file system.

# vi /etc/vfstab

The file system automatically mounts whenever the system boots.

Different file system types have unique properties that affect how the mount command functions.

By default, the mount command assumes it is mounting a ufs-type file system. However, when you are mounting a different type of file system, you might have to specify its type on the command line. You use the -F option with the mount command to specify the type of file system mounted. The file system type must be determinable from the

/etc/vfstab, /etc/default/fs, or /etc/dfs/fstypes files.

Because the mount commands need the file system type to function properly, the file system type must be explicitly specified or determined by searching the following files:

•  The /etc/vfstab file for the FS type field

•  The /etc/default/fs file for a local file system type

•  The /etc/dfs/fstypes file for a remote file system type

If the file system’s type has not been explicitly specified on the command line using the mount -F FStypeoption, the mount command examines the /etc/vfstab file to determine the file system’s type. The mount command makes this determination by using the file system’s block device name, raw device name, or mount point directory name.

If the mount command cannot determine the file system’s type by searching the /etc/vfstab file, the mount command uses the default file system type specified in either the /etc/default/fs file or the /etc/dfs/fstypes file, depending on whether the file system is local or remote.

The default local file system type is specified in the /etc/default/fs file by the line entry LOCAL=fstype.

The first line entry in the /etc/dfs/fstypes file determines the default remote file system type.

Using the fstypCommand

You can also use the fstyp command with the raw device name of the

disk slice to determine a file system’s type.

# fstyp /dev/rdsk/c0t0d0s7

Specifying an hsfs File System Type

To mount a file system that resides on a CD-ROM when the Volume Management services are stopped, as the root user perform the command:

# mount -F hsfs -o ro /dev/dsk/c0t6d0s0 /cdrom

In this example, the file system type is hsfs, the file system resides on disk slice /dev/dsk/c0t6d0s0, and the mount point /cdrom is a pre-existing directory in the Solaris OE.

Specifying a pcfs File System Type

To mount a file system that resides on a diskette when the Volume Management services are stopped, as the root user, perform the commands:

# mkdir /pcfs

# mount -F pcfs /dev/diskette /pcfs

In this example, the file system type is pcfs. This file system resides on the device /dev/diskette, and the mount point is /pcfs.

A file system is commonly unmounted if it needs to be checked and repaired by the fsck command, or if it needs to be backed up completely.

Some file system administration tasks cannot be performed on mounted file systems. To unmount a file system to prepare it for system maintenance, use the umount command.

Unmounting a file system by using the umount command removes it from the file system mount point and deletes its entry from the /etc/mnttab file.

Note – Notify users before unmounting a file system that they are currently accessing.

To unmount a file system manually by using the directory mount point, perform the command:

# umount /export/home

To unmount a file system manually by using the logical disk device name, perform the command:

# umount /dev/dsk/c0t0d0s7

The /etc/mnttab file is read by the /usr/sbin/umountall command during the system shutdown sequence or when umountall is invoked from the command line. The umountall unmounts all file systems

specified in the vfstab file except / (root), /usr, /proc, /dev/fd, /var,  /var/run, and /tmp.

Run the umountall command as the root user when you want to unmount manually all the file systems listed in the /etc/mnttab file, for example:

# umountall

To unmount only the local file systems listed in the /etc/mnttab file, perform the command:

# umountall -l

To verify that a file system or a number of file systems have been unmounted, invoke the mount command and check the output.

Any file system that is busy is not available for unmounting. Both the umount and umountall commands display the error message: umount: file_system_name busy

A file system is considered to be busy if one of the following conditions exists:

• l A program is accessing a file or directory in the file system

• l A user is accessing a directory or file in the file system

• l A program has a file open in that file system

• l The file is being shared

There are two methods to make a file system available for unmounting if it is busy:

• fuser command – Lists all of the processes that are accessing the file system and kills them if necessary

•  umount -f command – Forces the unmount of a file system

Note – The fuser command displays the process IDs of all processes currently using the specified file system. Each process ID is followed by a letter code. These letter codes are described in the man page for this command.

Using the fuserCommand

To stop all processes that are currently accessing a file system, follow these steps:

1. As the root user, list all of the processes that are accessing the file system. Use the following command to identify which processes need to be terminated.

# fuser -cu mount_point

This command displays the name of the file system and the user login name for each process currently active in the file system.

2. Kill all processes accessing the file system.

# fuser -ck mount_point

A SIGKILL message is sent to each process that is using the file system.

3. Verify that there are no processes accessing the file system.

# fuser -c mount_point

4. Unmount the file system.

# umount mount_point

Using the umount -fCommand

As the root user, you can unmount a file system, even if it is busy, by using the -f (force) option with the umount command. The following is the format for this command:

# umount -f mount_point

The file system is unmounted even if it contains open files. A forced unmount can result in loss of data and in zombie processes that are left running on the system. However, it is particularly useful for unmounting a shared file system if the remote file server is nonfunctional.

The following procedure describes how to boot from the Solaris OE Software CD-ROM to edit a misconfigured /etc/vfstab file.

1. Insert the Solaris 9 OE Software 1 of 2 CD-ROM into the CD-ROM drive.

2. Execute a single-user boot from the CD-ROM.

ok boot cdrom -s

Note – Performing a single-user boot operation from this software CD-ROM creates an in-memory copy of the /var file system, which supports your ability to perform administrative tasks.

3. Use the fsck command on the / (root) partition to check and repair any potential problems in the file system.

# fsck /dev/rdsk/c0t0d0s0

4. If the fsck command is successful, mount the / (root) file system on the /a directory to gain access to the file system on disk.

# mount /dev/dsk/c0t0d0s0 /a

5. Set and export the TERM variable, which enables the vi editor to work properly.

# TERM=sun

# export TERM

6. Edit the /etc/vfstab file, and correct any problems. Then exit the file.

# vi /a/etc/vfstab

# cd /

# umount /a

8. Reboot the system.

# init 6

To provide access to file systems on diskettes and CD-ROMs, the Solaris OE provides users a standard interface referred to as Volume Management.

Note – The Solaris 9 OE includes support for additional removable media such as DVDs, Jaz drives, Zip drives, and PCMCIA memory cards. (PCMCIA stands for Personal Computer Memory Card International Association.) For more information on using these devices, see the resources available on the Solaris 9 Documentation CD.

Volume Management provides two major benefits:

l It automatically mounts removable media for both the rootuser and non-root users.

l It can give other systems on the network automatic access to any removable media currently inserted in the local system.

The Volume Management service is controlled by the /usr/sbin/vold daemon. By default, this service is always running on the system so that it can automatically manage diskettes and CD-ROMs for regular users.

Volume Management features automatic detection of CD-ROMs. However, it does not detect the presence of a diskette that has been inserted in the drive until the volcheck command is run. This command instructs the vold daemon to check the diskette drive for any inserted media. Volume Management can mount ufs, pcfs, hsfs, and udfs file systems.

To make working with diskettes and CD-ROMs simple for your users, each device is easy to mount and mounts at an easy-to-remember location.

If the vold daemon detects that the mounted device contains a file system, then the device is mounted at the directory location.

Table 4-1 lists the directory locations of mounted devices that contain file

systems.

If the vold daemon detects that the mounted device does not contain a

file system, the device is accessible through a path.

• First diskette drive /floppy/floppy0

• First CD-ROM or DVDdrive  /cdrom/cdrom0

• First Jaz drive /rmdisk/jaz0

• First Zip drive /rmdrive/zip0

• First PCMCIA card /pcmem0

• First diskette drive /vol/dev/aliases/floppy0

• First CD-ROM or DVD drive /vol/dev/aliases/cdrom0

• First Jaz drive /vol/dev/aliases/jaz0

• First Zip drive /vol/dev/aliases/zip0

• First PCMCIA card /vol/dev/aliases/pcmem0

When Volume Management is running on the system, a regular user can easily access a diskette or CD-ROM by following these basic steps:

• Insert the media.

• For diskettes only, enter the volcheck command.

• Use the cd command to change to the directory of the mounted volume.

• Work with files on the media.

• Unmount the media.

• Eject the media.

/etc/vold.conf The Volume Management configuration file. This file defines  items, such as what action should be taken when media is inserted or ejected, which devices are managed by Volume Management, and which file system types are unsafe to eject. /etc/rmmount.conf The rmmount command configuration file. The rmmount command is a removable media mounter that is executed by the Volume Management daemon whenever a CD-ROM or diskette is inserted.

To restrict regular users from accessing diskettes or CD-ROMs on the system, you can, as the root user, terminate the Volume Management service.

To stop Volume Management from running on a system temporarily, as the root user perform the command:

# /etc/init.d/volmgt stop

To restart the Volume Management service, as the root user perform the command:

# /etc/init.d/volmgt start

If a CD-ROM fails to eject from the drive, as the root user attempt to stop Volume Management. If this is unsuccessful, kill the vold daemon.

# /etc/init.d/volmgt stop

or as a last resort:

# pkill -9 vold

Push the button on the system to eject the CD-ROM. The CD-ROM tray ejects. Remove the CD-ROM, and leave the tray out. Then restart the Volume Management service.

# /etc/init.d/volmgt start

Wait a few seconds, and then push the CD-ROM tray back into the drive.

When Volume Management is not running, only the root user can mount

and access a diskette or CD-ROM. Follow these steps:

1. Insert the media device.

2. Become the root user.

3. Create a mount point, if necessary.

4. Determine the file system type.

5. Mount the device by using the mount options listed in the following Sections.

6. Work with files on the media device.

7. Unmount the media device.

8. Eject the media device.

9. Exit the root session.

Using the mount Command

To mount a file system that resides on a CD-ROM when the Volume  Management services are stopped, as the root user, perform the command:

# mount -F hsfs -o ro /dev/dsk/c0t6d0s0 /cdrom

In this example, the file system type is hsfs, the file system resides on disk slice /dev/dsk/c0t6d0s0, and the mount point /cdrom is a pre-existing directory in the Solaris OE.

To mount a file system that resides on a diskette when the Volume Management services are stopped, as the root user, perform the command:

# mkdir /pcfs

# mount -F pcfs /dev/diskette /pcfs

In this example, the file system type is pcfs. This file system resides on the /dev/diskette device, and the mount point used is /pcfs.

each step describes what you should do, you must determine which

In this exercise, you complete the following tasks:

• Create mount points

• Mount file systems

• Specify mount options

This exercise requires a spare disk that contains four unmounted ufs file systems on Slices 0, 1, 3, and 4. Refer to the lecture notes as necessary to perform the tasks listed.

Complete the following tasks:

l Record the default mount options that are used by the / (root) file

system mounted on your system. Mount the file system found on

Slice 4 of your spare disk on the /morespace directory. Verify the

mount options applied to the /morespace file system.

(Steps 1–3 in the Level 2 lab)

l Create a new file in the /morespace file system that contains one line

of text. Record the modify time for this file. Use the ls command to

display the last access time for this file. Record the time value. Wait

one minute, and then display the file content. Again check and

record the last access time for this file.

(Steps 4–7 in the Level 2 lab)

l Unmount the /morespace file system. Remount the same file system

as /morespace, and use the noatime mount option. Again display

the content of your text file. Check and record the last access time for

it. Add a line to the /etc/vfstab file that mounts the /morespace

file system when the system reboots. Reboot the system by using the

reboot command, and verify that the /morespace file system is

mounted.

(Steps 8–11 in the Level 2 lab)

l Mount the file system on Slice 0 as /dir0. Mount the file system on

Slice 1 as /dir0/dir1. In a second terminal window, change to the

/dir0/dir1 directory. In the original terminal window, try to

unmount the /dir0/dir1 directory. Record the error messages.

Attempt to forcibly unmount the /dir0/dir1 directory. Record the

result. Attempt to use the pwd command in the second terminal

window. Record what happens.

(Steps 12–17 in the Level 2 lab)

In this exercise, you complete the following tasks:

l Create mount points

l Mount file systems

l Specify mount options

This exercise requires a spare disk that contains four unmounted ufs file systems on Slices 0, 1, 3, and 4. Refer to the lecture notes as necessary to perform the tasks listed.

In this exercise, you accomplish the following:

l Record the default mount options that are used by the / (root) file system mounted on your system. Mount the file system found on Slice 4 of your spare disk on the /morespace directory. Verify the mount options applied to the /morespace file system.

l Create a new file in the /morespace file system that contains one line of text. Record the modify time for this file. Use the ls command to display the last access time for this file. Record the time value. Wait one minute, and then display the file content. Again check and record the last access time for this file.

l Unmount the /morespace file system. Remount the same file system as /morespace, and use the noatime mount option. Again display the content of your text file. Check and record the last access time for it. Add a line to the /etc/vfstab file that mounts the /morespace file system when the system reboots. Reboot the system using the reboot command, and verify that the /morespace file system is mounted.

l Mount the file system on Slice 0 as /dir0. Mount the file system on Slice 1 as /dir0/dir1. In a second terminal window, change to the/dir0/dir1 directory. In the original terminal window, try to unmount the /dir0/dir1 directory. Record the error messages. Attempt to forcibly unmount the /dir0/dir1 directory. Record the result. Attempt to use the pwd command in the second terminal window. Record what happens.

Complete the following steps:

1. Log in as the root user, and open a terminal window. Use the mount

command to list the file systems that are currently mounted on your

system. What are the default mount options applied to the / (root)

file system?

2. Create the directory /morespace to use as the mount point.

3. Mount the file system on Slice 4 of your spare disk to the

/morespace directory. Record the default mount options that were

applied to this mount.

4. Change to the /morespace directory, and create a new file that has

one line of content.

5. Display a long listing for this file, and record the time value it

reports. This time value represents when the file was last modified.

6. Add the -u option to the ls command to show when the file was last

accessed. This time value is updated whenever you read the file.

7. Wait one minute or more, and then use the cat command to display

the file. Again check and record the access time. The access time

should differ from the access time indicated in the previous step.

8. Change to the / (root) directory. Unmount the /morespace file

system. Remount the same file system to the /morespace directory,

but add the option that prevents update of access time values. Verify

that the options to the mount were applied.

9. Return to the /morespace file system, and use the cat command to

display your test file. Again check and record the access time. The

access time should match the access time that existed prior to your

unmounting and mounting the /morespace file system.

10. Add a line to the /etc/vfstab file to make the mount for the

/morespace file system happen when you boot the system.

11. Reboot your system. Log in as the root user, and open a terminal

window. Use the mount command to verify that the /morespace file

system is mounted.

12. Create a directory called /dir0. Mount the file system that resides on

Slice 0 of your spare disk as /dir0.

13. Create a directory called /dir0/dir1. Mount the file system that

resides on Slice 1 of your spare disk as /dir0/dir1.

14. Open a second terminal window. In this new window, change the

directory to /dir0/dir1.

15. In your original terminal window, attempt to unmount the file

system mounted below the /dir0/dir1 directory. Which message is

displayed? Does the file system unmount?

Note – To discover why you could not unmount the file system, use the

fuser -cu /dir0/dir1 command. The fuser command should show

the process ID of the shell.

16. In your original terminal window, again attempt to unmount the file

system mounted below the /dir0/dir1 directory. Add the -f option

to the umount command. Which message is displayed? Does the file

system unmount?

17. In the second terminal window, attempt to determine your current

working directory. Which message is displayed? Change the

directory to / (root), and verify that the pwd command works.

In this exercise, you complete the following tasks:

l Create mount points

l Mount file systems

l Specify mount options

This exercise requires a spare disk that contains four unmounted ufs file

systems on Slices 0, 1, 3, and 4. Refer to the lecture notes as necessary to

perform the tasks listed.

In this exercise, you accomplish the following:

l Record the default mount options that are used by the / (root) file

system mounted on your system. Mount the file system found on

Slice 4 of your spare disk on the /morespace directory. Verify the

mount options applied to the /morespace file system.

l Create a new file in the /morespace file system that contains one line

of text. Record the modify time for this file. Use the ls command to

display the last access time for this file. Record the time value. Wait

one minute, and then display the file content. Again check and

record the last access time for this file.

l Unmount the /morespace file system. Remount the same file system

as /morespace, and use the noatime mount option. Again display

the content of your text file. Check and record the last access time for

it. Add a line to the /etc/vfstab file that mounts the /morespace

file system when the system reboots. Reboot the system using the

reboot command, and verify that the /morespace file system is

mounted.

l Mount the file system on Slice 0 as /dir0. Mount the file system on

Slice 1 as /dir0/dir1. In a second terminal window, change to the

/dir0/dir1 directory. In the original terminal window, try to

unmount the /dir0/dir1 directory. Record the error messages.

Attempt to forcibly unmount the /dir0/dir1 directory. Record the

result. Attempt to use the pwd command in the second terminal

window. Record what happens.

Complete the following steps:

1. Log in as the root user, and open a terminal window. Use the mount

command to list the file systems that are currently mounted on your

system. What are the default mount options applied to the / (root)

file system?

# mount

Your dev= number depends on the architecture of your system.

2. Create the directory /morespace to use as the mount point.

# mkdir /morespace

3. Mount the file system on Slice 4 of your spare disk to the

/morespace directory. Record the default mount options that were

applied to this mount.

# mount /dev/dsk/c1t3d0s4 /morespace

# mount

4. Change to the /morespace directory, and create a new file that has

one line of content.

# cd /morespace

# cat > testfile

5. Display a long listing for this file, and record the time value it

reports. This time value represents when the file was last modified.

# ls -l

6. Add the -u option to the ls command to show when the file was last

accessed. This time value is updated whenever you read the file.

# ls -lu

7. Wait one minute or more, and then use the cat command to display

the file. Again check and record the access time. The access time

should differ from the access time indicated in the previous step.

# cat testfile

# ls -lu

8. Change to the / (root) directory. Unmount the /morespace file

system. Remount the same file system to the /morespace directory,

but add the option that prevents update of access time values. Verify

that the options to the mount were applied.

# cd /

# umount /morespace

# mount -o noatime /dev/dsk/c1t3d0s4 /morespace

# mount

9. Return to the /morespace file system, and use the cat command to

display your test file. Again check and record the access time. The

access time should match the access time that existed prior to your

unmounting and mounting the /morespace file system.

# cd /morespace

# cat testfile

# ls -lu

10. Add a line to the /etc/vfstab file to make the mount for the

/morespace file system happen when you boot the system.

11. Reboot your system. Log in as the root user, and open a terminal

window. Use the mount command to verify that the /morespace file

system is mounted.

# init 6

# mount

12. Create a directory called /dir0. Mount the file system that resides on

Slice 0 of your spare disk as /dir0.

# mkdir /dir0

# mount /dev/dsk/c1t3d0s0 /dir0

13. Create a directory called /dir0/dir1. Mount the file system that

resides on Slice 1 of your spare disk as /dir0/dir1.

# mkdir /dir0/dir1

# mount /dev/dsk/c1t3d0s1 /dir0/dir1

14. Open a second terminal window. In this new window, change the

directory to /dir0/dir1.

# cd /dir0/dir1

15. In your original terminal window, attempt to unmount the file

system mounted below the /dir0/dir1 directory. What message is

displayed? Does the file system unmount?

# umount /dev/dsk/c1t3d0s1

# mount

Note – To discover why you could not unmount the file system, use the

fuser -cu /dir0/dir1 command. The fuser command should show

the process ID of the shell.

16. In your original terminal window, again attempt to unmount the file

system mounted below the /dir0/dir1 directory. Add the -f option

to the umount command. Which message is displayed? Does the file

system unmount?

# umount -f /dev/dsk/c1t3d0s1

# mount

17. In the second terminal window, attempt to determine your current

working directory. Which message is displayed? Change the

directory to / (root), and verify that the pwd command works.

# pwd

# cd /

# pwd