- 论坛徽章:
- 0
|
原帖由 kurt_wang 于 2006-12-19 19:23 发表
输出结果如下：
super-block at 00000001.0000
magic a501fcf5 version 4
ctime 1024024705 630275 (Fri Jun 14 11:18:25 2002 CDT)
log_version 9 logstart 0 logend 0
bsize 8192 size ...
...
flags 1 mod 0 clean 3c
...
flags是 "1" 意思是 "full fsck required"
no valid ILISTs for fileset 999 (incident 45311 refers)
On file systems created prior to VERITAS File System (VxFS) 3.3.2, if the primary inode list grows beyond 2 Gbytes, fsck may fail with the errors listed above. This problem has been reported as incident 45311. It is caused by VxFS not setting the largefiles flag on the structural fileset. The fsck included in VxFS 3.4 and later will handle this situation. A point patch is available for VxFS 3.3.3 patch 01 running on Solaris 2.6, 7 and 8. Please contact VERITAS Technical Support for more information on this point patch.
(VERITAS Incident Number 45311):
WARNING: Incident 45311 is NOT fixed in VxFS 3.3.3 Patch01. Original publication of this TechFile listed Incident 45311 as fixed in VxFS 3.3.3 Patch01. Fix for incident 45311 never made it to Patch01. It is, however, fixed in VxFS 3.4 and above. If it is not possible to upgrade to VxFS 3.4, then there is also a workaround. The workaround is to use a modified fsck binary for Solaris 2.6 and 7 only. Please contact VERITAS Technical Support to request fsck binary.
An "invalid size" error for the ilist inodes is displayed while running a full fsck on a VxFS file system that has grown beyond 2 gigabytes in size. This may prevent the file system from being mounted. Because the largefiles flag on the primary fileset was not set automatically, the error reported that the primary inode had an invalid size. This is a corner case situation that can occur after a VxFS upgrade from a previous version of VxFS that did not use the largefiles flag and the inode structural file had exceeded 2 gigabytes. |
|
免费注册
楼主: 萧瑟
发表于 2006-12-19 20:20
