Sponsored Content
Full Discussion: Make_recovery HP-UX 10.20
Operating Systems HP-UX Make_recovery HP-UX 10.20 Post 302777671 by vbe on Friday 8th of March 2013 09:02:05 AM
Old 03-08-2013
lvextend add physical extents (imagine pseudo disk blocks...) -L is to give the new size in MB...
here it can be done with sam but sam will complain because sam automatcally after will try to extend the filsystem which it can not...
Dont remember what happens after, mind you you can try... it wont brake anything...
It may show the logical volume size with the new size... in which case that part is done...
You can type the command now also...

you can give a new size to extendfs but I find it silly since what ever space you leave you cannot use it... only to extend the existing... not giving a size will make extendfs use all it finds... but remember umount first then usr raw device!
Good luck!

Looked at you link... Is this mounted in a rack? how is the disk connected? behind on the scsi 68pin? what is it used for?
 

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

aix mksysb , hpux make_recovery sun?

hi, for aix and hpux, we have both mksysb and make_recovery for restoring to the former state after it was crashed. is there any equivalent to sun? any pointers will be appreciated. thanks (8 Replies)
Discussion started by: yls177
8 Replies

2. HP-UX

HPUX make_recovery

I'm attempting to do a make_recovery on my HPUX box. My question revolves around the number of device files I have for my tape drive and what each one is intending for and which I should use. Some examples of my devices include 1m, 1mb, 1mnb, 2m, 2mb, 2mn, 2mnb, C1t0d0best, C1t0d0dds, &... (4 Replies)
Discussion started by: gonzotonka
4 Replies

3. HP-UX

Problems restoring Ignite make_recovery DAT backups

Can anyone help with an HP Ignite problem please !! We currently have 2 servers running HP-UX B.11.00 connected together and using a high availability cluster (serviceguard) running one package. Each of the servers have 2 mirrored local disks. (also installed HP OpenviewDM B.05.03, Oracle 8.0.5,... (7 Replies)
Discussion started by: clivethegadget
7 Replies

4. HP-UX

Make_Recovery Question Urgent Plse Respond

I have a make_recovery tape, if I restore the VG00 volume group using this, will my other volume groups still be ok after the restore(I have 7 data volume groups) I used make_recovery -A to create the tape I have a HP9000 HP-UX 11 An internal disk is failing, the other volume groups are on... (3 Replies)
Discussion started by: rees_a
3 Replies
device_maps(4)                                                     File Formats                                                     device_maps(4)

NAME
device_maps - device_maps file SYNOPSIS
/etc/security/device_maps DESCRIPTION
The device_maps file contains access control information about each physical device. Each device is represented by a one line entry of the form: device-name : device-type : device-list : where device-name This is an arbitrary ASCII string naming the physical device. This field contains no embedded white space or non- printable characters. device-type This is an arbitrary ASCII string naming the generic device type. This field identifies and groups together devices of like type. This field contains no embedded white space or non-printable characters. device-list This is a list of the device special files associated with the physical device. This field contains valid device special file path names separated by white space. The device_maps file is an ASCII file that resides in the /etc/security directory. Lines in device_maps can end with a `' to continue an entry on the next line. Comments may also be included. A `#' makes a comment of all further text until the next NEWLINE not immediately preceded by a `'. Leading and trailing blanks are allowed in any of the fields. The device_maps file must be created by the system administrator before device allocation is enabled. This file is owned by root, with a group of sys, and a mode of 0644. EXAMPLES
Example 1: A sample device_maps file # scsi tape st1: rmt: /dev/rst21 /dev/nrst21 /dev/rst5 /dev/nrst5 /dev/rst13 /dev/nrst13 /dev/rst29 /dev/nrst29 /dev/rmt/1l /dev/rmt/1m /dev/rmt/1 /dev/rmt/1h /dev/rmt/1u /dev/rmt/1ln /dev/rmt/1mn /dev/rmt/1n /dev/rmt/1hn /dev/rmt/1un /dev/rmt/1b /dev/rmt/1bn: FILES
/etc/security/device_maps SEE ALSO
allocate(1), bsmconv(1M), deallocate(1), dminfo(1M), list_devices(1) NOTES
The functionality described in this man page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for more information. SunOS 5.10 16 Jan 2001 device_maps(4)
All times are GMT -4. The time now is 08:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy