08-15-2008
this sounds oddly familiar.
10 More Discussions You Might Find Interesting
1. Solaris
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)
Discussion started by: sriram.s
4 Replies
2. Solaris
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. Solaris
Dear all,
I am very new to solaris,
I have installed solaris 10,
i tried installing few softwares into file system, unfortunately system failed to install stating "No space left on device "
i searched few threads and it says, we have to increase root size. where my root size is... (2 Replies)
Discussion started by: radhnki
2 Replies
4. HP-UX
Experts,
I want to know how to increase partion size in Hp-ux.Actually we installed oracle in separate part ion.As increase of database went to 99% :eek:.What ever data which is in it is important.so i dont want to delete any data in that partion.Now the size of that is 250 GB.I want the same to... (2 Replies)
Discussion started by: naveennella
2 Replies
5. Red Hat
Hi All,
this should be probably a already asked question but highly appreciate if someone can guide me on this
i have a business critical linux system (which is running a SMS system) where one of it's partition size is shrinking
i want to know the possible options of increasing the size of... (4 Replies)
Discussion started by: asela115
4 Replies
6. Solaris
I am trying to expand the root partition on Solaris 10. I can expand root partition using format/partition command, but usually increasing cylinders on partition is done on back end. In this case I would have to expand from the front end following the table below, meaning I would have to move the... (12 Replies)
Discussion started by: mjaminal
12 Replies
7. Red Hat
I have a RHEL6 guest running on vmware esx server and the root disk size is 30G and i increased the disk size and create another partition /dev/sda3 but i do not know how to increase the size of the VG and then intrun LV .. can anyone help me on this .
fdisk -l /dev/sda
Disk /dev/sda:... (1 Reply)
Discussion started by: fugitive
1 Replies
8. Red Hat
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
9. Red Hat
Hello Admins,
I am running a redhat linux 5 on vmware workstation.
I need to increase or add some more space to my root (/) partition. I don't have any LVM configured..
Please suggest.
# df -kh
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 3.8G 3.1G ... (4 Replies)
Discussion started by: snchaudhari2
4 Replies
10. Linux
Hi OS Experts
I would like to increase root partition from another partition so that I can save more documents in Home and Desktop. whether it is possible without formating root partition if so please explain
here is o/p of df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda9... (8 Replies)
Discussion started by: Akshay Hegde
8 Replies
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)