09-30-2010
Only root partition (/) is mirrored. /data, /opt and others are not.
10 More Discussions You Might Find Interesting
1. AIX
I have AIX 5.1
I ran these commands and was not able to see what disk were mirrored to what. I thought this is what I should do?
lslv -m rd |more
lslv -m db |more
I get a error stating that it can't find or in the device configuation databse.
Is there another way to look? I have a physcal... (1 Reply)
Discussion started by: rocker40
1 Replies
2. AIX
How do I know, which all disks are mirrored? any command?
Bala (7 Replies)
Discussion started by: balaji_prk
7 Replies
3. Solaris
Hi guys,
I havent done this before but iam trying to create an image of a mirrorred drive.
Correct me if iam wrong, but when i have two disks setup in raid configuration and have them mirrored in solaris. It then defines at one entity.
How would i create a "flar" image of that one entity... (3 Replies)
Discussion started by: tlee
3 Replies
4. HP-UX
Follwing up on what I was working on yesterday, I noticed that at this thread, someone was suggesting that you WOULDN'T want to mirror DUMP. When I boot with my current secondary disk (because I didn't mirror DUMP) I get an error indicating that DUMP isn't there. Why wouldn't I want to mirror... (1 Reply)
Discussion started by: deckard
1 Replies
5. Solaris
We use SW mirroring (RAID1) using SVM for our SUN servers (which we OEM to end clients with our application on). When I need to make a tape backup for the server (disk), I disable mirroring and perform backup of the entire disk to tape using ufsdump. This process requires an outage and sensitive as... (8 Replies)
Discussion started by: StarSol
8 Replies
6. UNIX for Advanced & Expert Users
I have a HP proliant ML 570 G3 with two 146GB disk drives mirrored(RAID1+0)
windows server 2003 was installed on that disk.
I will add a disk.(scsi 300GB)
I will install Linux on that additional disk.
I want to create multiple-boot system.
Is it possible?
I wanna know how to create... (0 Replies)
Discussion started by: lifegeek
0 Replies
7. HP-UX
hi every body
i want to know which command tell me more detailes to know the 2 disks mirrored or not ? in group like vg00 (5 Replies)
Discussion started by: maxim42
5 Replies
8. HP-UX
Hello All,
Am trynig to identify if the local HD's on our BL860 (running 11v3) are indeed mirrored to each other.
Cheers,
Cameron (3 Replies)
Discussion started by: Cameron
3 Replies
9. AIX
I want to increase the size of /tmp by 1GB
I know that the command is
chfs -a size=+1G /tmp
But the rootvg is mirrored and when I do a lsvg -p rootvg, I could see 2 disks.
Will there be any impact if I increase the size of /tmp when the rootvg is mirrored ?
Please advise. (1 Reply)
Discussion started by: newtoaixos
1 Replies
10. AIX
Hi all,
I need to extend a lv, but unfortunately I do not have enough space on my mirrored Volume group.
I've planned to add 2 more disks to this vg (for mirroring)
But ... what's the next steps to extend my lv using these 2 disks with a valid mirroring ?
1. extendvg myvg disk1 disk2... (3 Replies)
Discussion started by: unclefab
3 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)