Sponsored Content
Full Discussion: increasing root / partition
Operating Systems Solaris increasing root / partition Post 302485763 by jegaraman on Thursday 6th of January 2011 06:19:01 AM
Old 01-06-2011
increasing root / partition

Dear all,

I have a root partition which is 20 G in size. I have var and /tmp as seperate file systems. But this 20 G of root is not sufficeint.

I want to increase the size of the / partition.

Is there any way to increase with out down time.

my df -k output is

Code:
Filesystem             size   used  avail capacity  Mounted on
/dev/md/dsk/d0          20G    17G   2.6G    87%    /
/devices                 0K     0K     0K     0%    /devices
ctfs                     0K     0K     0K     0%    /system/contract
proc                     0K     0K     0K     0%    /proc
mnttab                   0K     0K     0K     0%    /etc/mnttab
swap                    24G   2.2M    24G     1%    /etc/svc/volatile
objfs                    0K     0K     0K     0%    /system/object
sharefs                  0K     0K     0K     0%    /etc/dfs/sharetab
fd                       0K     0K     0K     0%    /dev/fd
swap                    24G   304K    24G     1%    /tmp
swap                    24G    23M    24G     1%    /var/run
/dev/dsk/c6t600A0B800067BCDE000002A64B15CBB4d0s2
                        25G    15G   9.7G    61%    /oradata/db01
/dev/dsk/c6t600A0B800067BCDE000002A94B15CC16d0s2
                        25G   6.2G    18G    26%    /oradata/db02
/dev/dsk/c6t600A0B800067BCDE000002B54B15D391d0s2
                       9.8G   161M   9.6G     2%    /oradata/admin
/dev/dsk/c6t600A0B800067BCDE000002AD4B15D169d0s2
                        25G   7.0G    17G    29%    /oradata/db03
/dev/dsk/c6t600A0B800067BCDE000002B94B15D54Bd0s2
                        20G   1.4G    18G     8%    /oraarch
/dev/dsk/c6t600A0B800067BCDE000002B74B15D4F6d0s2
                        59G    44G    14G    76%    /orabkup
/dev/dsk/c6t600A0B800067BF47000004354BF9EEACd0s2
                        59G    34G    24G    59%    /orabkup1
/dev/md/dsk/d3          99G   6.6G    91G     7%    /ora1
/dev/dsk/c6t600A0B800067BCDE000002B34B15D325d0s2
                       9.8G    79M   9.7G     1%    /oradata/dba
/dev/lofi/126           94M   4.0M    80M     5%    /global/.devices/node@2
/dev/lofi/127           94M   4.0M    80M     5%    /global/.devices/node@1


Thanks and Regards
Rj

Last edited by DukeNuke2; 01-06-2011 at 08:15 AM..
 

10 More Discussions You Might Find Interesting

1. Solaris

Reinstall root partition

I had Solaris 8 installed on a Ultra 10 machine but during a shutdown the root partition got corrupted. I have 3 other partitions on the drive (var, swap, home). Is there a way to reinstall the root partition without effecting the other partitions? Also, when I run format from single user mode I... (4 Replies)
Discussion started by: jbestor
4 Replies

2. Solaris

Increasing size of Root Partition

Dear all, How can we increase the space for the root partition, ensuring that there is no loss of data in Solaris 9. How can the growfs command be utilized in this case. Thanks. (7 Replies)
Discussion started by: asadlone
7 Replies

3. UNIX for Dummies Questions & Answers

Best ways of increasing space on a partition

Hi, On one of our solaris servers, the root partition has filled up,(it was poorly sized in the first place), Does anyone have any advice about the best way to add space to a partition. I'm sure I've read how to do this somewhere before but just can't remember...:( A colleague has suggested... (1 Reply)
Discussion started by: kenny123m
1 Replies

4. UNIX for Dummies Questions & Answers

Increasing the Size of the Samba Partition

Hi, Is there any command to increase the size of the samba partition when the samba share is online?? Regards Arun (1 Reply)
Discussion started by: Arun.Kakarla
1 Replies

5. Solaris

Can't metattach root partition

I'm mirroring up a T2000. Able to metainit and metattach all partitions with the exception of root. Getting the following error: metattach: <hostname>; c1t1d0s0; is mounted on / I'm stumped. By the way, target 1 is the boot disk. (7 Replies)
Discussion started by: Probos
7 Replies

6. Red Hat

increase root partition

i am using redhat 5.4 and my root size shows 98 %, how can i increase root size # df -h Filesystem Size Used Avail Use% Mounted on /dev/sda2 77G 16G 75G 98% / /dev/sda1 2.4G 82M 2.2G 4% /boot tmpfs 3.8G 0 3.8G 0%... (8 Replies)
Discussion started by: reply.ravi
8 Replies

7. Solaris

Root partition filling up

I have a T1000 Sparc server that has a relatively small root partition which is 24Gb and a larger partition dedicated to /export/home that is approximately 100 Gb. We have a lot of data going to /var/audit and to /var/core/corefiles. Is there any non-destructive way to redirect files from... (4 Replies)
Discussion started by: goose25
4 Replies

8. Solaris

Need to partition root

Hello guys, I am using Solaris 10 x86 OS. While installing OS i have allocated entire 10 GB space to the root. Now i am not able to create new partition it says me "out of range" or "<cylinder number> not expected". Can someone please help me to allocated a default recommended space i.e 8GB or... (2 Replies)
Discussion started by: bhargav90
2 Replies

9. Red Hat

Increasing Root File Partition

Dear all , We have a root partition ( / ) in linux which has a very less space . And we need to increase the size of the root partition . There are no space in other file systems , so that i can take it from there and increase it. Just wanted to know if we get some SAN space , can we... (2 Replies)
Discussion started by: jegaraman
2 Replies

10. Red Hat

Increasing size of root partition

Dear All , We need to increase the size of the root partition in a RHEL server. The model is Product Name: SUN FIRE X4170 SERVER. Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol00 119G 47G 67G 41% /... (3 Replies)
Discussion started by: jegaraman
3 Replies
SYSTEMD-VERITYSETUP-GENERATOR(8)                           systemd-veritysetup-generator                          SYSTEMD-VERITYSETUP-GENERATOR(8)

NAME
systemd-veritysetup-generator - Unit generator for integrity protected block devices SYNOPSIS
/lib/systemd/system-generators/systemd-veritysetup-generator DESCRIPTION
systemd-veritysetup-generator is a generator that translates kernel command line options configuring integrity protected block devices (verity) into native systemd units early at boot and when configuration of the system manager is reloaded. This will create systemd- veritysetup@.service(8) units as necessary. Currently, only a single verity device may be se up with this generator, backing the root file system of the OS. systemd-veritysetup-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-veritysetup-generator understands the following kernel command line parameters: systemd.verity=, rd.systemd.verity= Takes a boolean argument. Defaults to "yes". If "no", disables the generator entirely. rd.systemd.verity= is honored only by the initial RAM disk (initrd) while systemd.verity= is honored by both the host system and the initrd. roothash= Takes a root hash value for the root file system. Expects a hash value formatted in hexadecimal characters, of the appropriate length (i.e. most likely 256 bit/64 characters, or longer). If not specified via systemd.verity_root_data= and systemd.verity_root_hash=, the hash and data devices to use are automatically derived from the specified hash value. Specifically, the data partition device is looked for under a GPT partition UUID derived from the first 128bit of the root hash, the hash partition device is looked for under a GPT partition UUID derived from the last 128bit of the root hash. Hence it is usually sufficient to specify the root hash to boot from an integrity protected root file system, as device paths are automatically determined from it -- as long as the partition table is properly set up. systemd.verity_root_data=, systemd.verity_root_hash= These two settings take block device paths as arguments, and may be use to explicitly configure the data partition and hash partition to use for setting up the integrity protection for the root file system. If not specified, these paths are automatically derived from the roothash= argument (see above). SEE ALSO
systemd(1), systemd-veritysetup@.service(8), veritysetup(8), systemd-fstab-generator(8) systemd 237 SYSTEMD-VERITYSETUP-GENERATOR(8)
All times are GMT -4. The time now is 09:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy