18.02.2014 Views

string

string

string

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

INCORRECT BLOCK COUNT I=int (should be<br />

int) CORRECT?<br />

Cause<br />

During phase 1, fsck(1M) determined that the specified inode pointed to a number<br />

of bad or duplicate blocks, so the block count should be corrected to the actual<br />

number shown.<br />

Action<br />

Generally you can answer yes to this question without harming the filesystem.<br />

See Also<br />

For more information on bad blocks, see the section on checking filesystem integrity<br />

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

index failed:full:index preceded by<br />

saveset name<br />

Cause<br />

This is a server which has several clients. It seems when the backup kicks off many<br />

the savesets are failing with the message listed below.<br />

godzilla<br />

* godzilla:index 2 retries attempted<br />

* godzilla:index sh: save: not found<br />

index failed:full:index<br />

Action<br />

Edit the /etc/init.d/networker file and change the nsrexecd startup line to<br />

include a -p option to specify the command search path :<br />

(/usr/sbin/nsr/nsrexecd -s masters -p /usr/sbin/nsr )<br />

> /dev/console<br />

86 Solaris Common Messages and Troubleshooting Guide ♦ October, 1998

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

Saved successfully!

Ooh no, something went wrong!