06-26-2007
I can drop the size of partition #7, it's empty. Woudl that allow me to increase root? (Without losing data in root?)
Thanks!
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
How do I create new disk slices taking space from an existing slice? Right now I have slice 6 (/usr) with 16G. I'd like to create slices 5 (/opt) and 7 (/export/home) and steal space from slice 6.
Thanks (3 Replies)
Discussion started by: kmgrady01
3 Replies
2. Solaris
Hi all,
we have an existing system that was configured using just one of the (two) internal disks. I want to mirror the disk using SVM, but have realised there is no free slice for creating the metadb's. Is there a workaround I can use for this?
In the past we have always kept slice 7 free -... (8 Replies)
Discussion started by: badoshi
8 Replies
3. SuSE
Hello Experts,
I am very new to unix environment.
Root filesystem in one of our Linux boxes has almost reached 100%. is there a procedure/ way to resize the root filesystem.
******************************************************
ld8331:/ # df -h|more
Filesystem Size Used... (2 Replies)
Discussion started by: ashok1784
2 Replies
4. Solaris
Hi all
I'm having difficulty setting up a proper disk structure on a 72GB HDD. The drive was previously part of a zfs pool. The zpool has ben destroyed and now I want to use the disk in a raid 5 array. I need to partition the disk accordingly though.
This is what the partition table currently... (7 Replies)
Discussion started by: notreallyhere
7 Replies
5. Red Hat
Hi Team,
Require your expertise on how to resize / partition.
This is VM.
Thank you.
Reggy
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 15G 13G 556M 96% /
/dev/sda1 965M 43M 873M 5% /boot
tmpfs 502M 0 ... (5 Replies)
Discussion started by: regmaster
5 Replies
6. Solaris
I am trying to resize my disk space to be bigger on my solaris server (Sun Fire V240)
this server and other windows servers are attached to a SAN disks, the disk I want to resize is on the SAN.
I have free space on the SAN disks so I added some space to the windows disks and I made some... (8 Replies)
Discussion started by: sofihdi
8 Replies
7. Red Hat
Hi,
I'm running a Red Hat Enterprise Linux Server release 5.3 (Tikanga) on VMWare. It is a production system for which I may not get downtime soon. I happened to resize a underlying disk and the changes are not reflecting in the fdisk ouput. Further details are as follows.
The disk which i... (3 Replies)
Discussion started by: maverick_here
3 Replies
8. SCO
I have SCO Openserver 5.0.5
Root partition is 96% full and I would like to make it bigger. How can this be done?
1) Can I use 'dd' to backup 'root' and then backup '/u' to a third hard disk, then divvy the primary hard disk to have a larger 'root' filesystem (i.e. previous root + u)
2) ... (5 Replies)
Discussion started by: grips03
5 Replies
LEARN ABOUT PHP
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)