Link to home
Start Free TrialLog in
Avatar of davemiles
davemiles

asked on

Solaris 10: EXCESSIVE DUPLICATE FRAGMENTS

Hi All,

I have the following error:
# fsck -o f /var
/dev/md/dsk/d13 IS CURRENTLY MOUNTED READ/WRITE.
CONTINUE? y

** /dev/md/dsk/d13
** Currently Mounted on /var
** Phase 1 - Check Blocks and Sizes
FRAGMENT 100872 DUP I=3895 LFN 88
FRAGMENT 100873 DUP I=3895 LFN 89
FRAGMENT 100874 DUP I=3895 LFN 90
FRAGMENT 100875 DUP I=3895 LFN 91
FRAGMENT 100876 DUP I=3895 LFN 92
FRAGMENT 100877 DUP I=3895 LFN 93
FRAGMENT 100878 DUP I=3895 LFN 94
FRAGMENT 100879 DUP I=3895 LFN 95
FRAGMENT 100936 DUP I=3895 LFN 96
FRAGMENT 100937 DUP I=3895 LFN 97
EXCESSIVE DUPLICATE FRAGMENTS I=3895
CONTINUE? y

FRAGMENT 9749 DUP I=3901 LFN 0
** Phase 1b - Rescan For More DUPS
FRAGMENT 9749 DUP I=271 LFN 5
FRAGMENT 100872 DUP I=3880 LFN 88
BAD STATE 0x52 TO BLKERR

How can I fix this?
And what might have caused it?


Thanks,

ASKER CERTIFIED SOLUTION
Avatar of yuzh
yuzh

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of davemiles
davemiles

ASKER

Bellow is the portion of the SUN Docs article that seems to apply to this situation, but the recomended action is N/A
Could you explan this furture...


Thanks,

fragment-number DUP I=inode-number

 

Solaris 10:



block-number DUP I=inode-number

 

Cause
Inode inode-number contains a block number fragment-number, which is already claimed by the same or another inode. This error condition might generate the EXCESSIVE DUP BLKS error message in phase 1 if inode inode-number has too many block numbers claimed by the same or another inode. This error condition invokes phase 1B and generates the BAD/DUP error messages in phases 2 and 4.

Solaris 10: Inode inode-number contains a block number block-number, which is already claimed by the same or another inode. This error condition might generate the EXCESSIVE DUP BLKS error message in phase 1 if inode inode-number has too many block numbers claimed by the same or another inode. This error condition invokes phase 1B and generates the BAD/DUP error messages in phases 2 and 4.

Action
N/A

>>recomended action is N/A
it means that you don't need to take any action, "fsck" fix it for you.