Vorweg: du hast dein /nfs/root verzeichnis schon freigegeben, oder?
Braucht einen eigenen Export-Punkt, weils ein anderes FS auf einem
anderen Device ist.
Wenn das passt:
Folgende Optionen in /etc/exports wären wahrscheinlich interressant:
1 | nohide This option is based on the option of the same name provided in
|
2 | IRIX NFS. Normally, if a server exports two filesystems one of
|
3 | which is mounted on the other, then the client will have to
|
4 | mount both filesystems explicitly to get access to them. If it
|
5 | just mounts the parent, it will see an empty directory at the
|
6 | place where the other filesystem is mounted. That filesystem is
|
7 | "hidden".
|
8 |
|
9 | Setting the nohide option on a filesystem causes it not to be
|
10 | hidden, and an appropriately authorised client will be able to
|
11 | move from the parent to that filesystem without noticing the
|
12 | change.
|
13 |
|
14 | However, some NFS clients do not cope well with this situation
|
15 | as, for instance, it is then possible for two files in the one
|
16 | apparent filesystem to have the same inode number.
|
17 |
|
18 | The nohide option is currently only effective on single host
|
19 | exports. It does not work reliably with netgroup, subnet, or
|
20 | wildcard exports.
|
21 |
|
22 | This option can be very useful in some situations, but it should
|
23 | be used with due care, and only after confirming that the client
|
24 | system copes with the situation effectively.
|
25 |
|
26 | The option can be explicitly disabled with hide.
|
27 |
|
28 | crossmnt
|
29 | This option is similar to nohide but it makes it possible for
|
30 | clients to move from the filesystem marked with crossmnt to
|
31 | exported filesystems mounted on it. Thus when a child filesys-
|
32 | tem "B" is mounted on a parent "A", setting crossmnt on "A" has
|
33 | the same effect as setting "nohide" on B.
|
ansonsten versuch mal in den export-options für dein
loopback-gemountetes FS mit anzugeben:
fsid=42
