18.02.2014 Views

string

string

string

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

DUP/BAD I=i OWNER=o MODE=m SIZE=s<br />

MTIME=t FILE=f REMOVE?<br />

Cause<br />

During phase 1, fsck(1M) found duplicate blocks or bad blocks associated with the<br />

file or directory specified after FILE=whose inode number appears after I= (with<br />

other information).<br />

Action<br />

To remove this file or directory, answer yes. If you end up removing more than a few<br />

files in this manner, data loss will result, so it might be preferable to restore the<br />

filesystem from backup tapes.<br />

See Also<br />

For more information on checking filesystems, see the section on checking filesystem<br />

integrity in the System Administration Guide, Volume I.<br />

int DUP I=int<br />

Cause<br />

Upon detecting a block that is already claimed by another inode, fsck(1M) prints<br />

the duplicate block number and its containing inode (after I=).<br />

Action<br />

In fsck(1M) phases 2 and 4, you will decide whether or not to clear these bad<br />

blocks. Before committing to repair with fsck(1M), you could determine which file<br />

contains this inode by passing the inode number to the ncheck(1M) command:<br />

# ncheck -iinum filesystem<br />

Alphabetical Message Listing 57

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!