How to correct "WARNING: ufs_readdir: bad dir, inumber = 9547, fs = / "
edited Oct 25, 2013 2:15AM in Oracle Solaris File Systems and Disk Management (MOSC) 8 commentsAnswered ✓
I recently installed a new version of Networker backup client on one of our servers. When I go to launch nsrwatch, I get the following error:
ld.so.1: nsrwatch: fatal: liblocktbl.so: open failed: No such file or directory
I went to check the symbolic links and things are not looking good. I actually created a directory where the link was pointing, and it creates a phantom directory. I am assuming that the UFS filesystem on / is hosed up. Is the only way to attempt to fix this booting into single user mode /dvd boot and running a fsck? This server is an LDOM on a T4-4 box. Could I shut down the ldom and run fsck from the service domain?
ld.so.1: nsrwatch: fatal: liblocktbl.so: open failed: No such file or directory
I went to check the symbolic links and things are not looking good. I actually created a directory where the link was pointing, and it creates a phantom directory. I am assuming that the UFS filesystem on / is hosed up. Is the only way to attempt to fix this booting into single user mode /dvd boot and running a fsck? This server is an LDOM on a T4-4 box. Could I shut down the ldom and run fsck from the service domain?
0