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 DOT edu or visit the list's Web site at
> http://listserv.temple.edu/archives/networker.html where you can
> also view and post messages to the list. Questions regarding this list
> should be sent to stan AT temple DOT edu
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=