Article Title: how to solve the file system fault of AIX. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.
During file system maintenance and management, you may encounter such problems, for example, you cannot install a file system or disassemble a file system. When a file system's super block is damaged, but the file system cannot be used normally. How to fix the main file system in rootvg is discussed below to solve some common file system problems.
1. Recover a super Block Error
When using the fsck or mount command, some users may encounter a problem with the super block of the file system when they see the following prompt:
fsck: Not an AIX3 file systemfsck: Not an AIXV3 file systemfsck: Not an AIX4 file systemfsck: Not an AIXV4 file systemfsck: Not a recognized file system typemount: invalid argument |
For example, when you install a/allenfs file system, the following error occurs:
Mount: 0506-324 Cannot mount/dev/lv1 on/allenfs: A system call has ed a parameter that is not valid.
When the file system is repaired, the following error message is displayed and an exception is terminated:
#fsck /dev/lv1Not a recognized filesystem type. (TERMINATED)
|
To solve this problem, we can only use the backup super block to restore the primary super block. We all know that in the file system, the Logical Block No. 1 is the primary super block, the No. 31 logical block is the backup super block, so the content on the No. 31 logical block is written to the No. 1 Logical Block.
For example, if the logical volume of the file system is/dev/lv1, the command to restore the super block of the file system is as follows:
#dd count=1 bs=4k skip=31 seek=1 if=/dev/lv1 of=/dev/lv1 |
When the recovery is complete, run the fsck command to check the integrity of the file system:
#fsck /dev/lv1** Checking /dev/rlv1 (/allen)** Phase 0 - Check Loglog redo processing for /dev/rlv00** Phase 1 - Check Blocks and Sizes** Phase 2 - Check Pathnames** Phase 3 - Check Connectivity** Phase 4 - Check Reference Counts** Phase 5 - Check Inode Map** Phase 6 - Check Block Map9 files 608 blocks 15776 free |
In many cases, restoring the backup super block to the primary super block can solve this problem and make the file system work normally. If the problem persists, you can only delete the file system, create a new file system, and restore the backup data.
2. Unable to disassemble the File System
If a user or program is active in a file system, the file system cannot be disassembled. When the command is run, the following error is prompted:
Device busy or A device is already mounted or cannot be unmounted. For example, due to the abnormal termination of the installation program or other reasons, the drive cannot be released normally (the drive is a cdrom File System, when you access the drive again, error 0514-062 occurs: the specified device is busy.
Follow these steps:
1. Check whether your current working directory is in this file system. If yes, run the cd/command to return the current working directory to the root directory, and then try again to disassemble the file system;
2. If the file system still cannot be detached, files may be opened in the file system. Therefore, close these files before disassembling the file system. Sometimes there may be some processes that are using the resources of this file system. You can use the fuser command to check that those processes are still active in this file system. The Fuser command displays the IDs of all active processes in the file system. The following is an example of using the fuser command:
#fuser /dev/cd/dev/cd: 2910 3466 |
If you use fuser? U/dev/cd indicates the user name after the process number. If the root user uses fuser? The k/dev/cd Command sends a SIGKILL signal to these processes to kill them. Run the kill command to kill the active processes and then try again to remove the file system. For example:
In this case, you can run the following command to check whether the device status is available:
Or
[1] [2] Next page
