Sponsored Content
Full Discussion: Find hdisk# based on LV name
Operating Systems AIX Find hdisk# based on LV name Post 302765679 by MichaelFelt on Sunday 3rd of February 2013 05:53:10 AM
Old 02-03-2013
Code:
lslv -m lvname | head

might give a nice starting point.

hope this helps

Last edited by zaxxon; 02-03-2013 at 12:23 PM.. Reason: code tags
This User Gave Thanks to MichaelFelt For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

AIX hdisk error

Does anyone have an idea what this means? hdisk10 is part of vg1. (vg1 has 11 hdisks) I get this msg every morning @ 5:04 CST This is the orignal message: A PROBLEM WAS DETECTED ON Fri Aug 17 03:02:09 PDT 2001 801014 The Service Request Number(s)/Probable Cause or... (2 Replies)
Discussion started by: Optimus_P
2 Replies

2. UNIX for Advanced & Expert Users

Find out which process is utilising a particular hdisk

Hi, Can anyone suggest how I can find out which process is keeping one of my hdisk constantly busy (100%) utilisation, when I ran topas . Thanks for your feedback Regards (2 Replies)
Discussion started by: tansha
2 Replies

3. AIX

vpath to an hdisk

Is there a simply way for me to map a vpath to an hdisk on AIX 5.2? (5 Replies)
Discussion started by: 2dumb
5 Replies

4. AIX

VPATHS and HDisk/not able to add to NR-VG

When I list the PV's using lspv i see both vpath and hdisk names being listed. I got the info that each vpath is configured for 4 hdisks. Problem is I am not able to add either the hard disks in vpath to the existing non-rootvg. ? need to know the basics of vpath .. (4 Replies)
Discussion started by: nivaspIND
4 Replies

5. AIX

load_balance or round_robin on hdisk

Hi, in an environment with svc's and ds8xxx wat disk algorithm should be used and what is the difference here: I can set the algorithm to Load_balance and to Round_robin (see output below). some info: hdisk3 ******** MPIO FC 2145 devices.sddpcm.53.rte 2.2.0.0 COMMITTED ... (1 Reply)
Discussion started by: raba
1 Replies

6. AIX

Dummy hdisk in AIX 6.1

How do you create a dummy hdisk with AIX 6.1? In previous versions, I've used this and works, but now I get this error. hostname:/:# mkdev -l hdisk57 -c disk -t osdisk -s scsi -p fscsi0 -w 0,10 -d Method error (/etc/methods/define): 0514-022 The specified connection is not valid. Any... (2 Replies)
Discussion started by: kah00na
2 Replies

7. AIX

Flashcopy, ghost hdisk ??

Hi all, I'm getting some errors on AIX regarding Flashcopy and volume group hard disks. The script that activates flashcopy showed this errors: Recreating Flashcopy for lun01_A1 Performing syntax check... Syntax check complete. Executing script... Script execution complete. SMcli... (1 Reply)
Discussion started by: enux
1 Replies

8. AIX

Quorum and hdisk issue

Hi. I found an issue with my appvg present in my server.my server is a single node and not part of hacmp. pmut3# lspv hdisk0 00c5c9cf92ebb96a rootvg active hdisk1 00c5c9cfcf30eee9 appvg hdisk2 00c5c9cfcf30ef98 ... (5 Replies)
Discussion started by: newtoaixos
5 Replies

9. Shell Programming and Scripting

Fetching hdisk sequence

Hi, Planning to implement script to fetch whether the hdisks are in proper sequence. Need output for incorrect sequence Correct #lspv hdisk0 hdisk1 hdisk2 :::::::::::: hdisk5 Incorrect sequence #lspv hdisk0 hdisk6 hdisk7 hdisk10 Any idea pls share (2 Replies)
Discussion started by: ksgnathan
2 Replies

10. AIX

How can I map hdisk# to rhdisk#?

Some storage/disks have been added to an existing AIX 6.1 server. The admin sent me the list of hdisk#'s for the new disks, but I need the corresponding rhdisk# for the same hdisk. (I know from past experience that the rhdisk that maps to an hdisk is not always the same number. For instance,... (5 Replies)
Discussion started by: sbrower
5 Replies
volume_key(8)						      System Manager's Manual						     volume_key(8)

NAME
volume_key - work with volume encryption secrets and escrow packets SYNOPIS
volume_key [OPTION]... OPERAND... DESCRIPTION
volume_key extracts "secrets" used for volume encryption (for example keys or passphrases) and stores them into separate encrypted "escrow packets", uses a previously created escrow packet to restore access to a volume (e.g. if the user forgets a passphrase), or manipulates the information in escrow packets. The mode of operation and operands of volume_key are determined by specifying one of the --save, --restore, --setup-volume, --reencrypt, --dump or --secrets options. See the OPTIONS sections for details. OPTIONS
In all options described below, VOLUME is a LUKS device, not the plaintext device containted within: blkid -s TYPE VOLUME should report TYPE="crypto_LUKS". The following options determine the mode of operation and expected operands of volume_key: --save Expects operands VOLUME [PACKET]. Open VOLUME. If PACKET is provided, load the secrets from it. Otherwise, extract secrets from VOLUME, prompting the user if necessary. In any case, store secrets in one or more output packets. --restore Expects operands VOLUME PACKET. Open VOLUME and use the secrets in PACKET to make VOLUME accessible again, prompting the user if necessary (e.g. by letting the user enter a new passphrase). --setup-volume Expects operands VOLUME PACKET NAME. Open VOLUME and use the secrets in PACKET to set up VOLUME for use of the decrypted data as NAME. Currently NAME is a name of a dm-crypt volume, and this operation makes the decrypted volume available as /dev/mapper/NAME. This operation should not permanently alter VOLUME (e.g. by adding a new passphrase); the user can of course access and modify the decrypted volume, modifying VOLUME in the process. --reencrypt Expects operand PACKET. Open PACKET, decrypting it if necessary, and store the information in one or more new output packets. --dump Expects operand PACKET. Open PACKET, decrypting it if necessary, and output the contents of PACKET. The secrets are not output by default. --secrets Expects operand PACKET. Open PACKET, decrypting it if necessary, and output secrets contained in PACKET. --help Show usage information. --version Show version of volume_key. The following options alter the behavior of the specified operation: -b, --batch Run in batch mode. Read passwords and passphrases from standard input, each terminated by a NUL character. If a packet does not match a volume exactly, fail instead of prompting the user. -d, --nss-dir DIR Use private keys in NSS database in DIR to decrypt public key-encrypted packets. -o, --output PACKET Write the default secret to PACKET. Which secret is the default depends on volume format: it should not be likely to expire, and it should allow restoring access to the volume using --restore. --output-data-encryption-key PACKET Write the data encryption key (the key directly used to encrypt the actual volume data) to PACKET. --output-passphrase PACKET Write a passphrase that can be used to access the volume to PACKET. --create-random-passphrase PACKET Generate a random alphanumeric passphrase, add it to VOLUME (without affecting other passphrases) and store the random passphrase into PACKET. -c, --certificate CERT Load a certificate from the file specified by CERT and encrypt all output packets using the public key contained in the certificate. If this option is not specified, all output packets are encrypted using a passphrase. Note that CERT is a certificate file name, not a NSS certificate nickname. --output-format FORMAT Use FORMAT for all output packets. FORMAT can currently be one of asymmetric (use CMS to encrypt the whole packet, requires a cer- tificate), asymmetric_wrap_secret_only (wrap only the secret, requires a certificate), passphrase (use GPG to encrypt the whole packet, requires a passphrase). --unencrypted Only dump the unencrypted parts of the packet, if any, with --dump. Do not require any passphrase or private key access. --with-secrets Include secrets in the output of --dump EXIT STATUS
volume_key returns with exit status 0 on success, 1 on error. NOTES
The only currently supported volume format is LUKS. EXAMPLE
Typical usage of volume_key proceeds as follows. During system installation or soon after, back up the default secret of a volume, and add a system-specific random passphrase. Encrypt both using a certificate: volume_key --save VOLUME -c CERT -o PACKET_DEFAULT --create-random-passphrase PACKET_PASSPHRASE Store PACKET_DEFAULT and PACKET_PASSPHRASE outside of the computer. If the user forgets a passphrase, and you can access the computer, decrypt PACKET_DEFAULT using the certificate private key (which should never leave a secure machine): volume_key --reencrypt -d NSS_DB PACKET_DEFAULT -o PACKET_DEFAULT_PW Then boot the computer (e.g. using a "rescue mode"), copy PACKET_DEFAULT_PW to it, and restore access to the volume: volume_key --restore VOLUME PACKET_DEFAULT_PW If the user forgets the passphrase, and you cannot access the computer, decrypt the backup passphrase: volume_key --secrets PACKET_PASSPHRASE and tell the backup passphrase to the user. (You can later generate a new backup passphrase.) volume_key Jun 2011 volume_key(8)
All times are GMT -4. The time now is 01:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy