I think Stef has the idea of what's wrong...
Are you attempting the restoral across different platforms?
As in where the target system does not support the file
system type that lived on the source system?
(Also: re "filespace not found" - please supply the full
message, including message number.)

   Richard Sims

On Nov 19, 2004, at 2:17 PM, Stef Coene wrote:

On Friday 19 November 2004 15:15, Otto Schakenbos wrote:

Richard, Mark, thnx for your answers.

I tried what you both suggested.
restore "/daten/" -subdir=yes and restore '/daten/' -subdir=yes

all with the same result. (filespace not found)

What I also tried is copy the data (the orginal server is still up)
using nfs to the new server and back it up from the new server using a
new nodename.
If i try to restore now it works just fine.

I inspected the orginal directory and couldent't really find anything
weird. The only thing I can think of is that there is a directory
(/daten/public) which is a nfs mount to another server but this has
never been a problem in the past.

Mark, you are right that there are more then 95 dirs, just to let you know.

What is the output of
dsmc q filespaces

And can you try to restore it via the GUI ?

And what kind of file system are you using ?

Stef

--
stef.coene AT docum DOT org
 "Using Linux as bandwidth manager"
     http://www.docum.org/