04-10-2009
You should login in single user mode to increase the space for /usr or /tmp or /var mount points.
9 More Discussions You Might Find Interesting
1. HP-UX
When taking a snap, I have a script that stops any active snap. When running the script, I'm getting a message that u02 and u04 are already mounted.
How can I find out what process(es) is/are latching on the these mount points?
Thank you for your time. (1 Reply)
Discussion started by: genzbeat
1 Replies
2. HP-UX
Hi,
Someone please help me with how i can unmount and remove all the files systems from a cluster. This is being shared by two servers that are active_standby. (3 Replies)
Discussion started by: joeli
3 Replies
3. OS X (Apple)
I have had a little issue with one of my disks, the usb cacble was pulled out and one of the external drives on it would no longer mount. I used First Aid and it verified and repaired both OK / nothing to do). After lots of messing around and not being able to mount I used Drive Genius 2 and that... (1 Reply)
Discussion started by: Cranie
1 Replies
4. Solaris
Hi
I have a mount point that is in production environment, and is currently filled up.
more space has been presented from same original source (EVA).
Problem;
1. Can't see presented space
2. After I discover the presented space, how do I go about adding this new space to existing mount point.... (9 Replies)
Discussion started by: Targ
9 Replies
5. Solaris
how to check how much space is occupied when u softmount or hard mount a file?
---------- Post updated at 03:24 AM ---------- Previous update was at 03:24 AM ----------
can anyone send me the answer (2 Replies)
Discussion started by: revathireddy
2 Replies
6. Shell Programming and Scripting
Hey there, sorry if this is a bit too much of a noob question, trying to get to grips with a simple bash script - but i have done ZERO bash scripting.
basically having worked out how to mount and unmount disks using:
disktool -m *device* & disktool -e *device*
- and looking at the result of... (2 Replies)
Discussion started by: hollister
2 Replies
7. Solaris
Hi, I need to expand a ZFS volume from 500GB to 800GB. I'd like to ask your help to confirm the following procedure:
Can I do it on the fly without bothering the users working on this volume?
Thank you in advance! (6 Replies)
Discussion started by: aixlover
6 Replies
8. Solaris
Hello I hope everyone is having a good day!
Situation:
2540 with 3.6TB of usable space
volume A is 2.6TB
volume B was 1TB
Volume A is mounted via a single lun on a solaris server and is running out of space.
Volume B was used on another server but is no longer, I deleted the volume in... (7 Replies)
Discussion started by: Metasin
7 Replies
9. Shell Programming and Scripting
Hi,
Need a bit of help on this one as I am a scripting noob.
I have a linux based NAS that mounts USB hard drives in an inconsistent location and to make matters worse, seems to lose the mount for an unknown reason and doesn't remount automatically unless the drive is removed and re-inserted.... (4 Replies)
Discussion started by: gtr33m
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)