I think you are out of luck unfortunately. UFS filesystems generally can't be grown. I believe your only choice would be to make a full backup, reinstall solaris laying out the filesystems how you want, then restore from your backup.
sry, but that's not true:
see:
you see? disksuite is complicated, but mighty.... if you are dealing with root partitions it's a pit more sophisticated. i am not sure if it will work to make a concat on the root partitions, never tried it, but i think it won't work. depending on how big your /export/home is you could dump it somewhere to, repartion your harddisk and increase the number of blocks for your root partition with the "format" menue, let the rootslice grow with "growfs", make a new fs on /export/home and restore the dump. i could imagine many ways to do it, e.g. you could use your second disk for /export/home, use the solaris feature to use a file for swapping (could be changed on the fly) and make new partitions on the 2nd disk and restore the system configuration...
but to be honest, if you are not used with solaris, it would be the easiest way for you to reinstall the system, sry
Quote:
Just Ice
also a way to do it, i like your script... but on that, you would need a downtime.... belongs to you
I tried to build a 1.3 TB volume with disk suite, and recieved an error (don't remember the exact verbage, it was very late). It only built a 1 TB volume. newfs completed without error. I rebuilt the volume to be just under 1TB, and all was fine. Is there a limitation with disk suite, or ufs, that... (3 Replies)
Hello all,
I'm ufs file system, how can u use the same disk in another machine with the data in tact? to make it clear, I've an ufs FS in a mount point /file1 ( 8GB). now they decide to reintall the OS. After the reinstall, how can i get the same data as it is? will mounting the disk as /file1... (3 Replies)
Hi
I am a bit green to AIX - but when our backup operator tries to do a restore from one AIX box to another, he get's the error:
'A file cannot be larger than the value set by ulimit'
I am wondering what is the impact of increasing the AIX filesize limit of 2 gb to unlimited. And how would... (1 Reply)
Hi frnz,
Need an urgent help...
I have installed solaris 8 in a sunblade workstation with 136GB hdd.
While installation it has taken a default filesystem size as 1.37GB for root.
AFtr completing the installation i have extended the root partition to 130GB.
But still df output shows... (4 Replies)
Hi All,
I am writing a block driver for a 2GB SD card where i get the total amount of data per request as follows:
struct request *req;
uint card_addr,total_bytes;
struct request_queue *rq = BlkDev->queue;
req = elv_next_request(rq);
..
..
card_addr = req->sector*512;... (1 Reply)
Hey all!
I was hoping someone knew anything about this one...
I know with Solaris Volume Manager the default Database Replica size is 8192 blocks (4MB approximately)
Now I know you can increase this amount but is there any point?
The reason I am asking this is that I've setup mirroring on... (2 Replies)
Hi,
I have recently taken up to support these SunOS 5.9 sun4u sparc SUNW,Sun-Fire-V240 boxes and got a request to increase the size of /backup01 as its getting filled up quickly and can't play much on it as these are production servers. As I have no idea about how to do this, can anyone let me... (0 Replies)
Hi
Please let me know how to increase the size of /tmp file system from 512m to 1024m dynamically without reboot in solaris zone
# df -h
Filesystem size used avail capacity Mounted on
zones/zone1 11G 1.0G 10.0G 10% /
/dev 11G 1.0G ... (6 Replies)
Discussion started by: sb200
6 Replies
LEARN ABOUT SUNOS
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)