Guest
|
Posted:
Tue Jan 25, 2005 7:01 pm Post subject:
Legato recover ls inconsistencies |
|
|
We are having some VERY strange behavior with Legato networker. Ther
version command replys a file is on tape but the ls command returns not
found. Below is the commands that we issued:
---------------------------------------------------------------
recover> version 180414db2-index1revprod.dbf.Z
Versions of `/pkg/db/180414db2-index1revprod.dbf.Z':
552 -rw-rw-r-- oracle dba 562897 Jan 18 04:23
180414db2-index1revproZ
save time: Tue Jan 18 04:31:19 2005
location: 00000156 at autochanger
recover> ls -l 180414db2-index1revprod.dbf.Z
recover: 180414db2-index1revprod.dbf.Z: not found
------------------------------------------------------------------------------------------------------------------------
When we did an "ls" to Legato to see if the file existed on tape,
legato came back with "not found". This was very strange in the fact
that the file had been on disk for more than 1 day. Legato also has a
version command that lists the different versions and savesets for a
particular filename. The version command displayed that legato did
think that the file is in the index. We use the ls command to verify
that files are on tape.
The strange thing is that a couple minutes later, we did an ls, and
then legato said it did have the file on tape.
I know I have seen this behavor in the past, and I think that is why
some of the old scripts do saves to legato and then immediately do a
verify to see if legato still knows it has the file.
If anyone has any idea what is going on with this I would greatly
appricate any information.
Dave Schaeffer
Bendix CVS LLC |
|
Hans Jørgen Jakobsen
Guest
|
Posted:
Tue Jan 25, 2005 9:14 pm Post subject:
Re: Legato recover ls inconsistencies |
|
|
On 25 Jan 2005 06:01:22 -0800, dave.schaeffer@gmail.com wrote:
| Quote: | We are having some VERY strange behavior with Legato networker. Ther
version command replys a file is on tape but the ls command returns not
found. Below is the commands that we issued:
---------------------------------------------------------------
recover> version 180414db2-index1revprod.dbf.Z
Versions of `/pkg/db/180414db2-index1revprod.dbf.Z':
552 -rw-rw-r-- oracle dba 562897 Jan 18 04:23
180414db2-index1revproZ
save time: Tue Jan 18 04:31:19 2005
location: 00000156 at autochanger
recover> ls -l 180414db2-index1revprod.dbf.Z
recover: 180414db2-index1revprod.dbf.Z: not found
------------------------------------------------------------------------------------------------------------------------
When we did an "ls" to Legato to see if the file existed on tape,
legato came back with "not found". This was very strange in the fact
that the file had been on disk for more than 1 day. Legato also has a
version command that lists the different versions and savesets for a
particular filename. The version command displayed that legato did
think that the file is in the index. We use the ls command to verify
that files are on tape.
The strange thing is that a couple minutes later, we did an ls, and
then legato said it did have the file on tape.
I know I have seen this behavor in the past, and I think that is why
some of the old scripts do saves to legato and then immediately do a
verify to see if legato still knows it has the file.
If anyone has any idea what is going on with this I would greatly
appricate any information.
Has the file been deleted from the local filesystem and there been made |
a backup after this event?
What browse date did you use in recover?
Try to change browse date to a time where the file excisted in the filesystem.
/hjj |
|