increasing root / partition Post: 302486676

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...

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.

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...

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

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.

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%...

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...

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...

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...

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% /...

LEARN ABOUT OPENSOLARIS

systemd-veritysetup-generator

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)