Sponsored Content
Full Discussion: disk adding through lvm
Operating Systems HP-UX disk adding through lvm Post 302115914 by sreekumar.R on Monday 30th of April 2007 02:01:03 AM
Old 04-30-2007
Dear Blow torch


I will follow this procedure .Thanks lot.

This topic is closed.
 

10 More Discussions You Might Find Interesting

1. HP-UX

Size of LVM header in non bootable disk

hi, i have a query regarding the size of the LVM header. Since the LVM header of a bootable disk is always 2912KB. The header size of a non bootable disk is not fixed. In Bootable disk after the LVM header (2912 KB=5824 sectors)the user data starts or we can say LV extents starts. If i extend any... (0 Replies)
Discussion started by: gorayen
0 Replies

2. AIX

Disk I/O Issue using LVM

We have a filesystem which contains 8 hard disks but i am facing disk I/O issue becuase data is not spreading across all the disks.Is there any way i can check how data is spreading and any parameter we need to change to spread ata across all disks. OS--AIX 5.3 (1 Reply)
Discussion started by: ukatru
1 Replies

3. HP-UX

Remove Faulty disk from HP-UX LVM VG

Requirement to remove a faulty mirrored disk from hp-ux LVM <root@pdwp1s>/etc # vgdisplay -v /dev/vg00 vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t0d0": The specified path does not correspond to physical volume attached to this volume group vgdisplay: Warning: couldn't... (9 Replies)
Discussion started by: Shirishlnx
9 Replies

4. Linux

About shrinking LVM and then adding the freed space to another OS on dualboot system

Hi all, Fedora 17, 64bit Ubuntu 12.04 desktop 64bit HD 160G I installed Ubuntu 12.04 on the HD first taking up the whole disc. Later I added/installed Fedora 17 selecting the "Shrink" option and save the bootloader on /dev/sda1 to make them dualboot. Installation is successful with... (0 Replies)
Discussion started by: satimis
0 Replies

5. Filesystems, Disks and Memory

LVM recovery, Hard disk broken

Hi I am new on your forum, because I need some help. I have a server with debian and proxmox 2. The HardDisk is broken. I am in rescue mode, and I can't mount LVM partition to recover my backups. What I've already done : # fdisk -l Disk /dev/sda: 2000.4 GB, 2000398934016 bytes 255... (0 Replies)
Discussion started by: pppplu
0 Replies

6. SuSE

Problem migrating disk attached to the same vg (lvm)

Hi, I'm trying to migrate the content of disk 'A' to disk 'B', that they belong to the same vg 'data'_vg'. Whe using pvmove, I get the following error: 'device-mapper: suspend ioctl failed: Interrupted system call'. I put down the whole trace: pvmove -v "source_disk" "sink_disk" ... (0 Replies)
Discussion started by: Begnux
0 Replies

7. UNIX for Advanced & Expert Users

LVM - restore metadata on other disk

Hi guys, I would like to ask your opinion about my theory, how to fix my broken LVM without risking any data loss. I use Archlinux at home. I just love this distro, even it gives me a lots of work (particularly after system updates). Basic system spec: AMD FX(tm)-6100 Six-Core Processor... (1 Reply)
Discussion started by: lyynxxx
1 Replies

8. HP-UX

LVM: is possible to replace a disk?

Scenario1: VG00 lvm,not mirrored,2 disk of 36GB vg size VG00 size is under 30G. Is possible to remove a disk of 36GB and replace "on fly" with a disk of 300GB on VG00? Thanks (6 Replies)
Discussion started by: Linusolaradm1
6 Replies

9. UNIX for Advanced & Expert Users

LVM, Troubles with adding another Disk

I am having trouble with LVM and one of my physical volumes. Using Ubuntu Desktop 14.04 I was trying to set up LVM across two disks (not containing the OS or Home). First I created the initial Physical Volume, the Volume Group, and the Logical volume, and everything seemed fine. The... (2 Replies)
Discussion started by: JR_ULFOR
2 Replies

10. UNIX for Advanced & Expert Users

[REDHAT7] Adding LVM volume

Dear community, is it possible to add more volumes to actual LVM disk? I have the following: # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 120G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 ... (0 Replies)
Discussion started by: Lord Spectre
0 Replies
TM::Bulk(3pm)						User Contributed Perl Documentation					     TM::Bulk(3pm)

NAME
TM::Bulk - Topic Maps, Bulk Retrieval Trait SYNOPSIS
my $tm = ..... # get a map from anywhere use TM::Bulk; use Class::Trait; Class::Trait->apply ($tm, 'TM::Bulk'); # give the map the trait # find out environment of topic my $vortex = $tm->vortex ('some-lid', { 'types' => [ 'types' ], 'instances' => [ 'instances*', 0, 20 ], 'topic' => [ 'topic' ], 'roles' => [ 'roles', 0, 10 ], 'members' => [ 'players' ], }, ); # find names of topics (optionally using a scope preference list) my $names = $tm->names ([ 'ccc', 'bbb', 'aaa' ], [ 's1', 's3', '*' ]); DESCRIPTION
Especially when you build user interfaces, you might need access to a lot of topic-related information. Instead of collecting this 'by foot' the following methods help you achieve this more effectively. names $name_hash_ref = $tm->names ($lid_list_ref, [ $scope_list_ref ] ) This method takes a list (reference) of topic ids and an optional list of scoping topic ids. For the former it will try to find the names (topic names for TMDM acolytes). If the list of scopes is empty then the preference is on the unconstrained scope. If no name for a topic is in that scope, some other will be used. If the list of scopes is non-empty, it directs to look first for a name in the first scoping topic, then second, and so on. If you want to have one name in any case, append "*" to the scoping list. If no name exist for a particular lid, then an "undef" is returned in the result hash. References to non-existing topics are ignored. The overall result is a hash (reference). The keys are of the form "topic-id @ scope-id" (without the blanks) and the name strings are the values. vortex $info = $tm->vortex (, $vortex_lid, $what_hashref, $scope_list_ref ) This method returns a lot of information about a particular toplet (vortex). The function expects the following parameters: lid: the lid of the toplet in question what: a hash reference describing the extent of the information (see below) scopes: a list (reference) to scopes (currently NOT honored) To control what exactly should be returned, the "what" hash reference can contain following components. All of them being tagged with <n,m> accept an additional pair of integer specify the range which should be returned. To ask for the first twenty, use "0,19", for the next "20,39". The order in which the identifiers is returned is undefined but stable over subsequent read-only calls. topic: fetches the toplet (which is only the subject locator, subject indicators information). names (<n,m>): fetches all names (as array reference triple [ type, scope, string value ]) occurrences (<n,m>): fetches all occurrences (as array reference triple [ type, scope, value ]) instances (<n,m>): fetches all toplets which are direct instances of the vortex (that is regarded as class here); instances* (<n,m>): same as "instances", but including all instances of subclasses of the vortex types (<n,m>): fetches all (direct) types of the vortex (that is regarded as instance here) types* (<n,m>): fetches all (direct and indirect) types of the vortex (that is regarded as instance here) subclasses (<n,m>): fetches all direct subclasses subclasses* (<n,m>): same as "subclasses", but creates reflexive, transitive closure superclasses (<n,m>): fetches all direct superclasses superclasses* (<n,m>): same as "superclasses", but creates reflexive, transitive closure roles (<n,m>): fetches all assertion ids where the vortex plays a role peers (<n,m>): fetches all topics which are also a direct instance of any of the (direct) types of this topic peers* (<n,m>): fetches all topics which are also a (direct or indirect) instances of any of the (direct) types of this topic peers** (<n,m>): fetches all topics which are also a (direct or indirect) instances of any of the (direct or indirect) types of this topic The function will determine all of the requested information and will prepare a hash reference storing each information into a hash component. Under which name this information is stored, the caller can determine with the hash above as the example shows: Example: $vortex = $tm->vortex ('some-lid', { 'types' => [ 'types' ], 'instances' => [ 'instances*', 0, 20 ], 'topic' => [ 'topic' ], 'roles' => [ 'roles', 0, 10 ], }, ); The method dies if "lid" does not identify a proper toplet. SEE ALSO
TM::Overview COPYRIGHT AND LICENSE
Copyright 200[3-57] by Robert Barta, <drrho@cpan.org> This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.10.1 2008-04-23 TM::Bulk(3pm)
All times are GMT -4. The time now is 10:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy