009 - Ist ein File Space das gleiche wie ein Filesystem?

The term file space in ISP is related to the OS term mounted file system.

In many cases a mounted filesystem, or more precisely a mount point to which a filesystem is mounted, is mapped to a file space.
However, the attributes of a file space also include the type of the file system.
Therefore e.g. a locally mounted filesystem /fs and a filesystem /fs mounted via network (NFS) with the same data will be stored in two different file spaces.

ISP divides the set of files stored for a node into file spaces which are managed completely separate from each other. The option "subdir=yes" does not mean the addition of all subdirectories, but only those which are in the same file space. The boundaries of the file spaces are initially determined by the configuration of the file systems on the source computers (on Unix systems, for example, by the boundaries of the file systems, under Windows by the drives). Each client administrator can create new boundaries and thus new file spaces by defining so-called virtual mount points (works for UNIX clients except Mac OS).

So you have to be aware that for ISP the world ends at the file space boundary. Therefore you can't usually get information about all your files by searching for "/*" using "-subdir=yes"; rather you have to do this search for each File Space separately.

An exotic but more insidious problem occurs when files end up in the wrong file space, such as the following:

1. The file space "/a" is set up.
2. The file "/a/b/c" is archived and ends up in the file space "/a".
3. The file space "/a/b" is created.
4. The file "/a/b/c" is searched for in the file space "/a/b" and consequently not found. In this case should have been explicitly searched for "{/a/}b/c".

To track such problems you need a list of file spaces, which you can get with the command "dsmc q filespace".