Le 7 déc. 05 à 11:50, Imad Soltani a écrit :
[EMAIL PROTECTED]:/opt/servletexec/ServletExecAS# fsck -n /dev/md/rdsk/d5 ** /dev/md/rdsk/d5 (NO WRITE) ** Last Mounted on /data ** Phase 1 - Check Blocks and Sizes 7589760 DUP I=896388 7589761 DUP I=896388 7589762 DUP I=896388 7589763 DUP I=896388 7589764 DUP I=896388 7589765 DUP I=896388 7589766 DUP I=896388 7589767 DUP I=896388 7589768 DUP I=896388 7589769 DUP I=896388 EXCESSIVE DUP BLKS I=896388 CONTINUE? no [EMAIL PROTECTED]:/opt/servletexec/ServletExecAS# voila pour le resultat je suppose qu'il est fache
N DUP I=N ========= Upon detecting a block that is already claimed by another inode, fsck(1M) prints the duplicate block number and its containing inode (after I=). In fsck phases 2 and 4, you will decide whether or not to clear these bad blocks. Before committing to repair with fsck, you could determine which file contains this inode by passing the inode number to the ncheck(1M) command: # ncheck -iinum filesystem For more information, see the chapter on checking filesystem integrity in the System Administration Guide,Volume I. _______________________________________________ Solaris_fr liste de diffusion en français pour Solaris, sur toutes architectures [email protected] http://x86.sun.com/mailman/listinfo/solaris_fr
