05-11-2012
Thank you Jlliagre,
That's a really good suggestion. Since you used the words "doomed link" I will forget that whole idea.
You say:
Quote:
what you might do is manually lofs mount your global zone directory to some directory under the zonepath.
something like
What do you mean by "manually mount"? Do you think that I can put this into the global vfstab to automate it? Do you think that this won't interfere with local zone booting/shutdown?
I realise that I need to test this but any information from someone who has more experience than me on this is extremely welcome. Although I've done loads of work on Solaris for years I have never had to tackle this particular issue.
Again, thank you immensely for your help on this.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
We use an WIN2000 NT Server and some Unix (Scitex Brisque) in our prepress network.
We want to create a folder onto the unix machine which is visible for the NTServer. The nfs apllication is Disk Acces.
The people at scitex told me to that I'd to make an export folder so the unix... (3 Replies)
Discussion started by: Vanstraelen
3 Replies
2. UNIX for Advanced & Expert Users
Hello,
We have an NFS problem :
when we try to automount or mount a share file system to a client we have the following error :
NFS acces failed for server xxxxx : error 7 (RPC : Authentication error).
We've have this error after the reboot of the client.
Rerun the automount daemon... (1 Reply)
Discussion started by: christophe
1 Replies
3. Solaris
Hello!
I have a Linux nfs server (called server100 below) with a export nfs. My problem is that the Solaris client (called client100 below) doesn't seems to like it. In the Solaris syslog I got following messages (and after a while the solaris client behave liked its hanged/to buzy). Also see... (3 Replies)
Discussion started by: sap4ever
3 Replies
4. UNIX for Dummies Questions & Answers
How can i create a nfs share in Windows? (4 Replies)
Discussion started by: proactiveaditya
4 Replies
5. Solaris
Hello,
I have a centos as nfs server, its name is centos_A.
After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/*
But,
My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Discussion started by: bruceharbin
1 Replies
6. HP-UX
Hi there!
I'm having problems migrating and vgimport onto a different server. Original server uses the legacy DSF naming (ctd naming like /dev/dsk/c0t1d0) and the new server where i'm migrating those luns to is using the Agile addressing (i.e persistent DSF i.e. /dev/disk/diskxxx)
Importing a... (1 Reply)
Discussion started by: ilan
1 Replies
7. UNIX for Advanced & Expert Users
Hello everyone!! Long time, no see!!
I have an issue with a Solaris server that I am working with. I am trying to set up a backup solution for someone that will involve a Solaris 9 server with NFS enabled allowing a Windows machine to map a drive to it (NFS Maestro).
NFS Maestro appears... (3 Replies)
Discussion started by: Jody
3 Replies
8. HP-UX
I am running HP9000 Containers version A.03.01. I have the container up and running. I now need to mount an exported file system from another HPUX server with both read and write permissions. I can get the mount okay but from the container I cannot read or write properly to the mounted file... (2 Replies)
Discussion started by: PaleRider
2 Replies
9. AIX
Hi 2 ALL,
try to run NFS Server in AIX 7.1 :
1. Step by step on NFS Server node
mkdir /tmp/test
chgrp staff /tmp/test
chmod 775 /tmp/test-- create export directory (fs)
mknfsexp -d /tmp/test -t ro
exportfs -va
show mount -e
:/# exportfs -av
exports: 1831-187 re-exported /tmp/test... (4 Replies)
Discussion started by: penchev
4 Replies
LEARN ABOUT OPENSOLARIS
lofs
lofs(7FS) File Systems lofs(7FS)
NAME
lofs - loopback virtual file system
SYNOPSIS
#include <sys/param.h>
#include <sys/mount.h>
int mount (const char* dir, const char* virtual, int mflag, lofs, NULL, 0);
DESCRIPTION
The loopback file system device allows new, virtual file systems to be created, which provide access to existing files using alternate
pathnames. Once the virtual file system is created, other file systems can be mounted within it, without affecting the original file sys-
tem. However, file systems which are subsequently mounted onto the original file system are visible to the virtual file system, unless or
until the corresponding mount point in the virtual file system is covered by a file system mounted there.
virtual is the mount point for the virtual file system. dir is the pathname of the existing file system. mflag specifies the mount options;
the MS_DATA bit in mflag must be set. If the MS_RDONLY bit in mflag is not set, accesses to the loop back file system are the same as
for the underlying file system. Otherwise, all accesses in the loopback file system will be read-only. All other mount(2) options are
inherited from the underlying file systems.
A loopback mount of '/' onto /tmp/newroot allows the entire file system hierarchy to appear as if it were duplicated under /tmp/newroot,
including any file systems mounted from remote NFS servers. All files would then be accessible either from a pathname relative to '/' or
from a pathname relative to /tmp/newroot until such time as a file system is mounted in /tmp/newroot, or any of its subdirectories.
Loopback mounts of '/' can be performed in conjunction with the chroot(2) system call, to provide a complete virtual file system to a
process or family of processes.
Recursive traversal of loopback mount points is not allowed. After the loopback mount of /tmp/newroot, the file /tmp/newroot/tmp/newroot
does not contain yet another file system hierarchy; rather, it appears just as /tmp/newroot did before the loopback mount was performed
(for example, as an empty directory).
Examples
lofs file systems are mounted using:
mount -F lofs /tmp /mnt
SEE ALSO
lofiadm(1M), mount(1M), chroot(2), mount(2), sysfs(2), vfstab(4), lofi(7D)
NOTES
All access to entries in lofs mounted file systems map to their underlying file system. If a mount point is made available in multiple
locations via lofs and is busy in any of those locations, an attempt to mount a file system at that mount point fails unless the overlay
flag is specified. See mount(1M). Examples of a mount point being busy within a lofs mount include having a file system mounted on it or it
being a processes' current working directory.
WARNINGS
Because of the potential for confusing users and applications, you should use loopback mounts with care. A loopback mount entry in
/etc/vfstab must be placed after the mount points of both directories it depends on. This is most easily accomplished by making the loop-
back mount entry the last in /etc/vfstab.
SunOS 5.11 10 Apr 2001 lofs(7FS)