Original physical systems: Sun Blade 100s running Solaris 10
I have managed to use the ldmp2v(1M) utility to turn one of these systems into a client LDOM of the host system (using the downloaded ISO file sol-10-u11-ga-sparc-dvd.iso):
Unfortunately I have just noticed that the root file system of this LDOM is now full:
Contents of /etc/vfstab: /dev/dsk/c0d0 is a ZFS volume on the host system, and the client file systems are, as you can see, UFS.
So the question is: Can I increase the size of the LDOM root partition easily, and if so, how? The alternative is to destroy this LDOM and recreate it using the -m option to ldmp2v to increase the size of the root partition. Not a problem, but not something I want to keep doing every time I get something wrong.
Hi All,
one of the mount point in Hp ux server has reached 95%
its a data base file and can not be deleted.
so i want to know how to increase the size of mount point
i am new to unix ,please help me (1 Reply)
Hi all,
I have a 130gb HDD of which 95b is taken up by various partitions of windows xp...
I partitioned my HDD and gave solaris 10gb of space, but now owing to some development stuff i need to increase the space!!!
How do i do it!!
Please note that i do have ~20gb of space left still...... (2 Replies)
Hello,
I am working AIX VIO server and extended Virtual Disk of one of the Partition with 10GB. After starting partition, i am not able to see increased size of disk.
Can you please help me what I need to do to increase the size of virtual disk from partition?
Thanks
Kishor
... (7 Replies)
hi guys
I am working on my vmware workstation.
I have a /dev/sdb which is 5GB. I am using LVM.
Now I increase /dev/sdb 2 more GB.
fdisk -l shows 7 GB but pvscan still shows 5GB.
how do I make my system recognize the new 7GB added and be able to add those to my physical volumen and... (1 Reply)
Hi Experts,
I have a problem wih /var. Disk /var is full. After i investigate, i found file /var/log/syslog.0 is growing rapidly. The size is 4.3G. I tried to move syslog.0 to another disk and file was moved successfully.
My question is why size /var can't increase? used space still 100%.
... (7 Replies)
Hi
I am using oracle linux 6.4. My hard drive capacity is 500 GB. my filesystem size onbly 50GB. I would like to extend my filesystem size to around 100GB. I tried many codes but still I am not able.
this is the output of df -h :
Filesystem Size Used Avail Use% Mounted on... (6 Replies)
Hi,
i installed Solaris 11 in T2000.
I have 2 guest domains, and i want to install Solaris 10 on a guest domain and Solaris 9 on another.
I added a vdsdev with the iso file to primary, and then i added a vdisk to guest domain but it doesnt recognize as boot disk.
I even tried with lofiadm -a... (6 Replies)
Hi,
There is LDOM Guest where I need to expand /u02 file systems on it.
It is residing on a Solaris 11 Hypervisor (Primary Domain).
The storage is expanded on vdisk presented to Hypervisor.
I need steps to expand the /u02 on LDOM Guest. (2 Replies)
Hi,
I'm Linux administrator who happens to 'administer' SCO Unix 5.0.7, which is virtual server on VMware - deployed from official ovf image.
My problem is that root filesystem is almost out of disk space, and we've decided to do it as we do on every other virtual servers and extend disk on... (13 Replies)
Discussion started by: goldenboy
13 Replies
LEARN ABOUT OSX
volfs
volfs(7FS) File Systems volfs(7FS)NAME
volfs - Volume Management file system
DESCRIPTION
volfs is the Volume Management file system rooted at root_dir. The default location for root-dir is /vol, but this can be overridden using
the -d option of vold (see vold(1M)). This file system is maintained by the Volume Management daemon, vold, and will be considered to be
/vol for this description.
Media can be accessed in a logical manner (no association with a particular piece of hardware), or a physical manner (associated with a
particular piece of hardware).
Logical names for media are referred to through /vol/dsk and /vol/rdsk. /vol/dsk provides block access to random access devices. /vol/rdsk
provides character access to random access devices.
The /vol/rdsk and /vol/dsk directories are mirrors of one another. Any change to one is reflected in the other immediately. The dev_t for a
volume will be the same for both the block and character device.
The default permissions for /vol are mode=0555, owner=root, group=sys. The default permissions for /vol/dsk and /vol/rdsk are mode=01777,
owner=root, group=sys.
Physical references to media are obtained through /vol/dev. This hierarchy reflects the structure of the /dev name space. The default per-
missions for all directories in the /vol/dev hierarchy are mode=0555, owner=root, group=sys.
mkdir(2), rmdir(2), unlink(2) (rm), symlink(2) (ln -s), link(2) (ln), and rename(2) (mv) are supported, subject to normal file and direc-
tory permissions.
The following system calls are not supported in the /vol filesystem: creat(2), only when creating a file, and mknod(2).
If the media does not contain file systems that can be automatically mounted by rmmount(1M), users can gain access to the media through the
following /vol locations:
+-----------------------------------+------------------------------------+
| Location | State of Media |
+-----------------------------------+------------------------------------+
|/vol/dev/diskette0/unnamed_floppy | formatted unnamed floppy-block |
| | device access |
+-----------------------------------+------------------------------------+
|/vol/dev/rdiskette0/unnamed_floppy | formatted unnamed floppy-raw |
| | device access |
+-----------------------------------+------------------------------------+
|/vol/dev/diskette0/unlabeled | unlabeled floppy-block device |
| | access |
+-----------------------------------+------------------------------------+
|/vol/dev/rdiskette0/unlabeled | unlabeled floppy-raw device access |
+-----------------------------------+------------------------------------+
|/vol/dev/dsk/c0t6/unnamed_cdrom | CD-ROM-block device access |
+-----------------------------------+------------------------------------+
|/vol/dev/rdsk/c0t6/unnamed_cdrom | CD-ROM-raw device access |
+-----------------------------------+------------------------------------+
For more information on the location of CD-ROM and floppy media, see System Administration Guide: Basic Administration or rmmount(1M).
Partitions
Some media support the concept of a partition. If the label identifies partitions on the media, the name of the media becomes a directory
with partitions under it. Only valid partitions are represented. Partitions cannot be moved out of a directory.
For example, if disk volume 'foo' has three valid partitions, 0, 2, and 5, then:
/vol/dsk/foo/s0
/vol/dsk/foo/s2
/vol/dsk/foo/s5
for block access and
/vol/rdsk/foo/s0
/vol/rdsk/foo/s2
/vol/rdsk/foo/s5
for character access.
If a volume is relabeled to reflect different partitions, the name space changes to reflect the new partition layout.
A format program can check to see if there are others with the volume open and not allow the format to occur if it is. Volume Management,
however, does not explicitly prevent the rewriting of a label while others have the volume open. If a partition of a volume is open, and
the volume is relabeled to remove that partition, it will appear exactly as if the volume were missing. A notify event will be generated
and the user may cancel the operation with volcancel(1), if desired.
SEE ALSO volcancel(1), volcheck(1), volmissing(1)rmmount(1M), vold(1M), rmmount.conf(4), vold.conf(4)
System Administration Guide: Basic Administration
SunOS 5.10 8 Feb 1995 volfs(7FS)