string

BAD/DUP FILE I=i OWNER=o MODE=m SIZE=s
MTIME=t CLEAR?
Cause
While checking inode link counts during phase 4, fsck(1M) found a file (or
directory) that either does not exist or exists somewhere else.
Action
To clear the inode of its reference to this file or directory, answer yes. With the -p
(preen) option, fsck(1M) automatically clears bad or duplicate file references, so
answering yes to this question seldom causes a problem.
Bad file number
Cause
Generally this is a program error, not a usage error.
Action
Contact the vendor or author of the program for an update.
Technical Notes
Either a file descriptor refers to no open file, or a read(2) (or write(2)) request is
made to a file that is open only for writing (or reading).
The symbolic name for this error is EBADF, errno=9.
block no. BAD I=inode no.
Cause
Upon detecting an out-of-range block, fsck(1M) prints the bad block number and
its containing inode (after I=).
22 Solaris Common Messages and Troubleshooting Guide ♦ October, 1998