Sponsored Content
Full Discussion: Resizing the Root Filesystem
Operating Systems Solaris Resizing the Root Filesystem Post 302417205 by Reboot on Thursday 29th of April 2010 12:21:53 AM
Old 04-29-2010
No....!!!!
I don't think you can resize Root File System.So, no question of reboot.
You should plan it (size) correctly during O.S installation keeping future requirements in mind.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Mounted Root Filesystem

In my Solaris 10 based server, I have noticed the following mounts when a use DF -K /dev/dsk/c0t0d0s0 5062414 3213876 1797914 65% / / 5062414 3213876 1797914 65% /net/se420 I understand the first mount because it appears in my vfstab file and is the mount of root that I would expect.... (1 Reply)
Discussion started by: jimthompson
1 Replies

2. Linux

/root filesystem size is full

hi in my server ( / ) root filesystem size is full how to reduce the size and what are the files i want to remove. i need answer for linux and AIX also. (6 Replies)
Discussion started by: chomca
6 Replies

3. Solaris

Move root filesystem to other slice

Hi, df -h display: # df -h Filesystem size used avail capacity Mounted on /dev/dsk/c1t0d0s0 9.8G 8.1G 1.7G 84% / /proc 0K 0K 0K 0% /proc mnttab 0K 0K 0K 0% /etc/mnttab fd 0K 0K 0K 0% /dev/fd swap 1.0G 152K 1.0G 1% /var/run swap 1.1G 24M 1.0G 3% /tmp /dev/dsk/c1t0d0s3 57G 13G 43G 24%... (4 Replies)
Discussion started by: lamoul
4 Replies

4. Solaris

Root Filesystem

Hi, Can we install root file system on other than 0th slice???? (5 Replies)
Discussion started by: tirupathiraju_t
5 Replies

5. UNIX for Dummies Questions & Answers

Root filesystem filling up!

Hi all. New to the forum and new to Unix admin... / filesystem filled up and I can't find where the large files are. Any help will be apppreciated: # df -k Filesystem kbytes used avail capacity Mounted on /dev/dsk/c1t0d0s0 8063580 7941745 41200 100% / /proc ... (4 Replies)
Discussion started by: jamie_collins
4 Replies

6. Linux

Encrypt already install root filesystem

All, Is there a way to encrypt my Ubuntu root HD after installation? (1 Reply)
Discussion started by: markdjones82
1 Replies

7. Linux

root filesystem goes readonly

I see this when tried to create a dir using root fstab entries are pretty normal tried to remount with rw but it is still the same block device /dev/sda2 is write-protected ---------- Post updated at 04:57 PM ---------- Previous update was at 03:51 PM ---------- fstab entry ... (4 Replies)
Discussion started by: robo
4 Replies

8. Red Hat

Resizing root virtual disk on the CentOS

Hello, Can someone suggest me what I missing, I re-sized a root virtual disk to 30GB on the CentOS VM. After re-sizing the disk, I booted the OS and ran fdisk -list command I was able view the size of the disk as 30GB. Paritions in the vm before I resize are: /boot - Primary parition /... (1 Reply)
Discussion started by: bobby320
1 Replies

9. Red Hat

How to resize filesystem by resizing the LUN without impact to applications.?

Is it possible to resize a filesystem by resizing the LUN on RHEL 6.4 64-bit with LVM and no impact to running applications? The research I have done so far seems to take the approach of adding a new LUN and then expaning the volume group to the new LUN. I'm looking for an approach that avoids a... (7 Replies)
Discussion started by: aenagy
7 Replies
semmnu(5)							File Formats Manual							 semmnu(5)

NAME
semmnu - maximum number of System V IPC undo structures for processes VALUES
Failsafe Default Allowed values DESCRIPTION
Note: If the DynSysVSem optional product bundle is installed then this tunable is ignored and has no effect. Applications can perform "undo" operations without any system imposed limits. The tunable specifies the maximum number of System V IPC system-wide processes that can have "undo" operations pending at any given time. If an application exhausts this limit, it will receive an error from For more information about System V semaphores, refer to the section of the sema(5) manpage. Who Is Expected to Change This Tunable? Anyone. Restrictions on Changing Changes to this tunable take effect at the next reboot. Note: If the DynSysVSem optional product bundle is installed then changes to this tunable are ignored and have no effect. When Should the Value of This Tunable Be Raised? When the set of application processes which use semaphore "undo" semantics exceeds the limit. When Should the Value of This Tunable Be Lowered? If requirements for semaphore "undo" semantics has significantly decreased, or for limiting protection on run-away applications which change semaphores. What Other Tunable Values Should Be Changed at the Same Time? All the System V semaphore tunables are interrelated and should not be treated as independent variables. The tunables must be evaluated as a system to ensure they reflect the application requirements. The semaphore tunables include and Generally, a change in does not require attention to other tunables. Note: If the DynSysVSem optional product bundle is installed then the and tunables are ignored and have no effect. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. A two-dimensional table of undo structures (~8 bytes each) is allocated in kernel memory at boot time. This memory is reserved whether or not it is used. The table dimensions are and (maximum number of per-process undo structures). So the memory requirement is approximately the product of those two tunables and the structure size. Use care when setting these two tunables, as they can have a profound effect on memory utiliza- tion, due to the multiplicative effect. Note: If the DynSysVSem optional product bundle is installed then and are ignored and have no effect. No memory is allocated at boot time. Instead "undo" structures are dynamically allocated when needed by the application and deallocated when no longer needed. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by AT&T. SEE ALSO
semop(2), sema(5), semaem(5), semmns(5), semmni(5), semmsl(5), semume(5), semvmx(5), sysv_hash_locks(5). Tunable Kernel Parameters semmnu(5)
All times are GMT -4. The time now is 05:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy