Re: TSM error
2000-11-15 07:24:14
Good morning!
This error generally points to a corrupt file. Here is a procedure for it:
ANS1028S - Corrupted file
1. Review dsmerror.log file to determine where the corrupted files is
located.
/var/adm/dsmerror.log
11/08/00 00:43:57 TransErrno: Unexpected error from lstat, errno = 89
11/08/00 00:43:57 PrivIncrFileSpace: Received rc=131 from
fioGetDirEntries: /
da /lost+found/49171
11/08/00 00:43:57 ANS1028S Internal program error. Please see your
service
representative.
2. Review the directory that shows the bad file.
root#f99999:/var/adm:cd /da
root#f99999:/da:ls
46D_45B bin housekeeping output
46d_kernel bw_scripts kernel restore
anke db.cfg.wbd.10-31 lost+found scripts
backup dbm.cfg.wbd.10-31 monitor scripts_r3r
root#f99999:/da:cd lost+found
root#f99999:/da/lost+found:ls
49171
root#f99999:/da/lost+found:file *
49171: directory
root#f99999:/da/lost+found:cd 49171
root#f99999:/da/lost+found/49171:ls
msg_server
By doing the following command, it will let you know if the file is corrupt.
root#f99999:/da/lost+found/49171:file *
msg_server: 0653-901 Cannot get file status.
Due to the status this file is in, you will be unable to delete it.
root#f99999:/da/lost+found/49171:rm msg_server
rm: msg_server: Invalid file system control data detected.
The only way you will be able to delete the file is to use the 'unlink'
command.
Warning: This command is very powerful so be sure that you do not have any
files or directories below the current structure that you want to get rid
of.
If you have numerous files in the current directory, move them to a
temporary directory so that you only have the corrupted file left. Then go
back one directory level and issue the command 'unlink xxxxx', with the
directory name being 'xxxxx'. This will unlink the directory and any files
underneath it.
If you were required to move any files, you can now re-create the directory
and move the files back.
Have a good day!
Brenda
|
|
|