+ <title>Examples</title>
+ <para>The following example will mount the
+ <literal>chipfs</literal> filesystem on client1 and create a
+ subdirectory <literal>v1_1</literal> within that filesystem. Client2
+ will then mount only the <literal>v1_1</literal> subdirectory as a
+ fileset, thereby limiting access to anything else in the
+ <literal>chipfs</literal> filesystem from client2.</para>
+ <screen>client1# mount -t lustre mgs@tcp:/chipfs /mnt/chip
+client1# mkdir /mnt/chip/v1_1</screen>
+ <screen>client2# mount -t lustre mgs@tcp:/chipfs/v1_1 /mnt/chipv1_1</screen>
+ <para>You can check the created mounts in /etc/mtab. It should look like
+ the following:</para>
+ <screen><replaceable>client1</replaceable>
+mds@tcp0:/chipfs/ /mnt/chip lustre rw 0 0
+</screen><screen>
+<replaceable>client2</replaceable>
+mds@tcp0:/chipfs/v1_1 /mnt/chipv1_1 lustre rw 0 0</screen>
+ <para>Create a directory under the /mnt/chip mount, and get its FID</para>
+ <screen>client1# mkdir /mnt/chip/v1_2
+client1# lfs path2fid /mnt/chip/v1_2
+[0x200000400:0x2:0x0]
+</screen>
+ <para>If you try resolve the FID of the <literal>/mnt/chip/v1_2</literal>
+ path (as created in the example above) on client2, an error will be returned
+ as the FID can not be resolved on client2 since it is not part of the
+ mounted fileset on that client. Recall that the fileset on client2 mounted
+ the <literal>v1_1</literal> subdirectory beneath the top level
+ <literal>chipfs</literal> filesystem.
+ </para>
+ <screen>client2# lfs fid2path /mnt/chip/v1_2 [0x200000400:0x2:0x0]
+fid2path: error on FID [0x200000400:0x2:0x0]: No such file or directory</screen>
+ <para>Subdirectory mounts do not have the <literal>.lustre</literal>
+ pseudo directory, which prevents clients from opening or accessing files
+ only by FID.</para>
+ <screen>client1# ls /mnt/chipfs/.lustre
+ fid lost+found</screen>
+ <screen>client2# ls /mnt/chipv1_1/.lustre
+ ls: cannot access /mnt/chipv1_1/.lustre: No such file or directory
+ </screen>