fsck如何解決AIX的文件系統(tǒng)故障

1、fsck如何解決aix的文件系統(tǒng)故障how does fsck resolve the file system failure of aixin 2009-04-20 the plaguefor file system maintenance and management in the process, will encounter some problems, such as can't in stall the file system or remove the file system, when the file system，s super block was damaged,

2、 and can't be used normal file system, how to repair the main file system anyway, here is to discuss how to solve the problem of some common file systems.one, restore the super block errorwhile some users are using fsck or mount commands, they may be a problem with the file system's super bl

3、ock 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 argumentfor example, when a user installs a/allenfs file system, thefollowing error message ap

4、pears:# mount/allenfsmount: 0506-324 cannot mount/dev/lvl on/allenfs: a system call received a parameter that is not validwhen the file system is fixed, the following error message appears and terminates:# fsck/dev/lvlnot a recognized filesystem typeto solve this problem, can only use the backup of

5、the super block to restore the super block, as we all know, in the file system, logic block is the main super block 1, 31 logic block is backup super block, so the content of the logical block on the 31st wrote 1 logical block up.for example, the file system，s logical volume is /dev/lvl, and the hyp

6、erblock command for the file system is restored as follows:dd count = 1 bs 二 4k skip 二 1 if 二 /dev/lvl of 二 /dev/lvlwhen the recovery is complete, the fsck command is used to check the integrity of the file system: # fsck/dev/lvl* * checking /dev/rlvl (/ allen)* * phase 0 - check loglog redo process

7、ing for /dev/rlvoo * phase 1 一 check blocks and sizes* phase 2-check pathnames* phase3 一 check connectivity* phase 4 - checkreference counts* * phase 5-checkinode map* phase- check block map9 files 608 blocks of 15776 freein many cases, this problem can be solved by restoring the backup superblock t

8、o the main super block, making the file system working under normal conditions if this doesn，t solve the problem, it can only remove the file system and then rebuild the file system and restore the backup data.two, unable to remove file systemif a user or a program in a file system activity, will no

9、t be able to remove the file system, when using remove commands, you will be prompted the following error:device busy or a device is already mounted or always be unmounted for example because of the installation program terminates abnormally or other reasons often cannot normal release drives (optic

10、al drive is a problem of cdrom file system), when users visit cd-rom drive again an error 0514-062: the specified device is busyfollow these steps to solve:1, check the user whether or not his current working directory in the file system, if it is, use cd/command return the current working directory

11、 to the root directory, and then tried to remove the file system;2, if still can，t remove the file system, which may be used in file system has a file is being opened up, so before remove the file system should be close the file sometimes there may be a few processes that are using the resource of t

12、his filesystem,you can use the fuser command to check that the processes are still active in the file system the fuser command displays all process id numbers that are active in the file system here's an example of the fuser command:# the fuser/dev/cd/ dev/cd: 2910 3466if you use the fuser - u/d

13、ev/cd, you will point the user name after the process number if the root user is using the fuser-k/dev/cd command, the process is given a sigkill signal to kill the process. then kill the active process with the kill command, and then try to disassemble the file system. such as:# mil 一 9, 2910, 3466

14、at this point, you can check the status of the device using the following command:# lsdev - cc cdromor# lsdev-c-1 cdo(if other file systems, will cdo in the logical name of the file system) as if the device status to available, you can use the equipment or unmount the filesystem.3, if the file syste

15、m is still in a busy state, cannot be removed, may be in the file system to load a kernel extension, the situation with the fuser command fails to check into the kernel extensions, check system provides a kernel extensions tools - genkex, use this command displays the current loaded all extension of

16、 the kerne1.4, if the system is installed in a single file to another file system, is to directly remove the file system is not successful, you must install this file system all file systems, removed to remove yourself using the mount command to see what are the file system was installed on the syst

17、em, and then according to the installation will be installed in all other files in the file system with the umount command removed, try to remove themselves again.unable to delete file systemwhen a file system can be installed with the mount command or unmounted by unmount, but the file system canno

18、t be deleted, the system will report the following error when removed:0516-306: unable to find in the device confgiguration data the reason for this error may be that the definition in the odm database is not the same as it is. you can check the type of file system with the following command:# lsvg

19、-1 anywayif the type is shown as? in the case of synclvodm-p rootvg and the syncvg-v rootvg command, the volume group is synchronized, and then the correct file type is displayed with the command lsvg -1 rootvg. the file system can be successfully deletedfix the main hie systems and logs in rootvgif

20、 you want to check and repair the anyway /, / tmp, / usr, / var file system, you must first uninstall them, however, in normal multi-user environment is unable to uninstall the file system and to do all this work should be carried out in maintenanee modefirst to reset the system, the system boot tim

21、e press f6 (for graphical way) or digital "6 key (the character) into the system of online diagnosis (online diagnostics) service mode, select into single user mode, name 1 y the maintenance modeif the current aix is aix 3. 2. 4 or 3. 2. 5, the odmdir environment variable must be set, as follow

22、s:# odmdir 二 / etc/objrepos; export odmdirrun the fsck command to clean up the file system mentioned above, and the command is as follows:# fsck/dev/hd4# fsck/dev/hd2# fsck/dev/hd3# fsck/dev/hd9varthe fsck option is also available if the default file system，s log (jfslog) in rootvg has a problem wit

23、h/dev/hd8, it can be rebuilt as follows:# logform/dev/hd8it will then prompt you to continue initialization, and if you answer y, the log information on/dev/hd8 is cleared.when the initialization is successful, the exit command exits the single-user mode, and the file system is automatically install

24、ed, depending on the prompt to enter the multiuser mode. finally, the shutdown command closes the system.for file system maintenance and management in the process, will encounter some problems, such as can，t install the file system or remove the file system, when the file system's super block wa

25、s damaged, and can，t be used normal file system, how to repair the main file system anyway, here is to discuss how to solve the problem of some common file systemsone, restore the super block errorwhile some users are using fsck or mount commands, they may be a problem with the file system，s super b

26、lock 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 argumentfor example, when a user installs a/allenfs file system, the following error message

27、appears:# mount/allenfsmount: 0506-324 cannot mount/dev/lvl on/allenfs: a system call received a parameter that is not validwhen the file system is fixed, the following error message appears and terminates:# fsck/dev/lvlnot a recognized filesystem typeto solve this problem, can only use the backup o

28、f the super block to restore the super block, as we all know, in the file system, logic block is the main super block 1, 31 logic block is backup super block, so the content of the logical block on the 31st wrote 1 logical block up.for example, the file system，s logical volume is /dev/lvl, and the h

29、yperblock command for the file system is restored as follows:dd count = 1 bs = 4k skip 二 1 if 二 /dev/lvl of 二 /dev/lvlwhen the recovery is complete, the fsck command is used to check the integrity of the file system:# fsck/dev/lvl * * checking /dev/rlvl (/ allen)* * phase 0 一 check loglog redo proce

30、ssing for /dev/rlvoophase1 一 check blocks and sizesphase2-check pathnamesphase一 checkconnectivityphase一 checkreferencecounts* phase5-checkinode mapphase一 checkblock mapfiles608 blocks of 15776freein many cases, this problem can be solved by restoring the backup superblock to the main super block, ma

31、king the file system working under normal conditions if this doesn，t solve the problem, it can only remove the file system and then rebuild the file system and restore the backup data.two, unable to remove file systemif a user or a program in a file system activity, will not be able to remove the fi

32、le system, when using remove commands, you will be prompted the following error:device busy or a device is already mounted or always be unmounted for example because of the installation program terminates abnormally or other reasons often cannot normal release drives (optical drive is a problem of c

33、drom file system), when users visit cd-rom drive again an error 0514-062: the specified device is busyfollow these steps to solve:1, check the user whether or not his current working directory in the file system, if it is, use cd/command return the current working directory to the root directory, an

34、d then tried to remove the file system;2, if still can，t remove the file system, which may be used in file system has a file is being opened up, so before remove the file system should be close the filesometimes there may be some process in the use of the file system resources, still can use the fus

35、er command to check what process activities in the file system the fuser command displays all process id numbers that are active in the file system here，s an example of the fuser command:# the fuser/dev/cd/ dev/cd: 2910 3466if you use the fuser - u/dev/cd, you will point the user name after the proc

36、ess number if the root user is using the fuser-k /dev/cd command, the process is given a sigkill signal to kill the process then kill the active process with the kill command, and then try to disassemble the file system such as:# mil 一 9, 2910, 3466at this point, you can check the status of the devi

37、ce using the following command:# lsdev - cc cdromor# lsdev-c-1 cdo(if other file systems, will cdo in the logical name of the file system) as if the device status to available, you can use the equipment or unmount the filesystem.3, if the file system is still in a busy state, cannot be removed, may

38、be in the file system to load a kernel extension, the situation with the fuser command fails to check into the kernel extensions, check system provides a kernel extensions tools - genkex, use this command displays the current loaded all extension of the kerne1.4, if the system is installed in a sing

39、le file to another file system, is to directly remove the file system is not successful, you must install this file system all file systems, removed to remove yourself. using the mount command to see what are the file system was installed on the system, and then according to the installation will be

40、 installed in all other files in the file system with the umount command removed, try to remove themselves againunable to delete file systemwhen a file system can be installed with the mount command or unmounted by unmount, but the file system cannot be deleted, the system will report the following

41、error when removed:0516-306: unable to find in the device confgiguration data the reason for this error may be that the definition in the odm database is not the same as it is. you can check the type of file system with the following command:# lsvg -1 anywayif the type is shown as? in the case of synclvodm-p rootvg and the syncvg-v rootvg command, the volume group is synchronized, and then the correct file type is displayed with the command lsvg t rootvg. the file system can be successfu