Backup Central

We have a Tru64 client (V5.1 1885 alpha), and save starts looping
instantly when saving that filesystem. It gets stuck in a read() loop,
when doing a trace on the process. I have tried both 6.1.4 and 7.1.3 on
the client, but both misbehave in the same way. This only occurs on one of
the filesystems on the client. ls -lR on the filesystem works just fine.
Anyone have a clue if this is a bug in something or what?

//Oscar

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

Hi Oscar,

Start running the save command enabling verbose (-v param).
You will get the name of the dir or file causing problem.
Maybe is it a looping hard linked file/dir ....
ls -lR just list the contents of the directory, not opens the
files as save does to read the contents of.

Knowing the impacted file/dir, you will then be
able to use tar or vdump doing more tests but,
the worst case could be the visible part of the corrupted
FS iceberg ...

HTH,

Th

We have a Tru64 client (V5.1 1885 alpha), and save starts looping
instantly when saving that filesystem. It gets stuck in a read() loop,
when doing a trace on the process. I have tried both 6.1.4 and 7.1.3 on
the client, but both misbehave in the same way. This only occurs on one of
the filesystems on the client. ls -lR on the filesystem works just fine.
Anyone have a clue if this is a bug in something or what?

//Oscar

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu


Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu

On Thu, 7 Apr 2005, Oscar Olsson wrote:

We have a Tru64 client (V5.1 1885 alpha), and save starts looping
instantly when saving that filesystem. It gets stuck in a read() loop,
when doing a trace on the process. I have tried both 6.1.4 and 7.1.3 on
the client, but both misbehave in the same way. This only occurs on one of
the filesystems on the client. ls -lR on the filesystem works just fine.
Anyone have a clue if this is a bug in something or what?

Take a look in that client's /nsr/logs/messages and /nsr/logs/daemon.log
file for information on this issue. I have seen the same thing happen when
someone created a recursive symbolic link and another time where there was
a directory path with some insanely large number of levels.

Note: To sign off this list, send a "signoff networker" command via email
to listserv < at > listserv.temple.edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
should be sent to stan < at > temple.edu