06-06-2011
Re-Hello,
I have another problem : i want to mount the same Lun on 2 different servers and at the end I have 2 different mounted points !
10 More Discussions You Might Find Interesting
1. Red Hat
Hello,
I'm trying to help a guy out on a VMWARE server, running what looks like a cut down version of redhat? 2.4.9-vmnix2 ...
Bascially the box serves vm clients via allocating a LUN from a SAN.. to cut a long story short, I need to find out which SAN the luns are comming from (could be 1... (0 Replies)
Discussion started by: itsupplies
0 Replies
2. UNIX for Dummies Questions & Answers
Hi,
We recently purchased a 3 tb RAID. In the setup, it created 2 slices, one 2 tb and one 1 tb slice. Right now only the 2 tb slice is visible when booting up. I was told that the second slice needs to be mapped to a lun and a port like the first slice is.
Does anyone know how I would go... (1 Reply)
Discussion started by: user23
1 Replies
3. Solaris
hey guys i got this in my logs what does this mean: (1 Reply)
Discussion started by: sbn
1 Replies
4. Solaris
I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer.
thanks (4 Replies)
Discussion started by: uuontario
4 Replies
5. AIX
Hello all,
I have the following env:
* DS4300 storage SAN
* AIX 5.3 Lpar (storage through vio server)
* AIX 5.3 Server
Some FS are too small do I'm setting up a process to increase the size of the FS.
To expand the size of the FS I plan to do the following for the physical AIX server,... (1 Reply)
Discussion started by: petervg
1 Replies
6. AIX
Aix 6.1, working with a nim master and nim_altmaster
both LPARS have access to the same data LUN, /nimdisk
I do realize the risks of having 2 servers access the same LUN, however it serves the purpose of being able to restore mksysb's to/from our DR site if necessary, at least in theory ;)
... (3 Replies)
Discussion started by: mshilling
3 Replies
7. Red Hat
Hi ALL,
what are the steps to detect and configure a new attached lun in RHEL 5.3.
rgds,
snj. (2 Replies)
Discussion started by: snjksh
2 Replies
8. Red Hat
Hi,
Is there command to detect the newly added LUN is linux box. I tried with below commands, but that doesn't work out.
fdisk -l,
fdisk -l | grep Disk
pvscan (5 Replies)
Discussion started by: gsiva
5 Replies
9. Emergency UNIX and Linux Support
I have a LUN (From HP-Storage VA7110) that is claimed on 2 servers, but is in used in one of the VG on Server-1 .
Now I want to shut Server-1 and re-use that LUN on server-2 .
Server-1
Path-1 : /dev/rdsk/c4t0d1
Path-2: /dev/rdsk/c6t0d1
Server-2
Path-1: /dev/rdsk/c5t0d1
Path-2:... (8 Replies)
Discussion started by: Shirishlnx
8 Replies
10. AIX
Hi,
I am not getiting lun id information on VIO Server. I have used the command fget_config command.
just showing # prompt.
I would like know wheather any other command is there equiv of fget_config
which will display lun id? (4 Replies)
Discussion started by: manoj.solaris
4 Replies
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)
WARNINGS
Loopback mounts must be used with care; the potential for confusing users and applications is enormous. 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.10 10 Apr 2001 lofs(7FS)