0506-324 Cannot Mount File System & # 40; transferred from the network & # 41

Problem description: failed to install the file system: 0506-324 Cannot Mount File System.

There are many situations that lead to this error message, and this article introduces a situation that causes this problem: the logical volume of this file system is used as the primary / secondary dump device of the system.

[@ more@]

Answer:

1. Check the file system information using the following command:

# lsvg-l vgname (assuming vgname is the name of the volume group that contains the file system)

Find out the display information for this file system:

Lvname jfs 7 7 1 open/syncd / fsname

two。 Use the fuser command to check if the process of taking advantage of secondary logical volumes:

# fuser-cux / dev/lvname = > No information is returned

Note: if the fuser command returns a set of processes related to the logical volume, you can resolve the installation of the file system by killing the corresponding processes.

3. Check if this logical volume is used as the primary / secondary dump device:

# sysdumpdev-l

Primary / dev/dumplv

Secondary / dev/lvname

Copy directory / var/adm/ras

Forced copy flag TRUE

Always allow dump FALSE

Dump compression OFF

If the primary dump device is set to / dev/lvname, use the following command to point the primary dump device to hd6 or a logical volume of type "sysdump": # sysdumpdev-Pp / dev/dump_lvname

If the secondary dump device is set to / dev/lvname, point the secondary dump device to / dev/sysdumpnull using the following command:

# sysdumpdev-Ps / dev/sysdumpnull

4. Look at the logical volume lvname again, and its properties should be changed from "open/syncd" to "closed/syncd":

# lsvg-l vgname

Lvname jfs 7 7 1 closed/syncd / fsname5. Use the fsck command to check the integrity of the file system before mount the file system:

# fsck / dev/lvname

6. Install the file system again with success:

# mount / fsname