Re: ??: Disks used by LV
From: Green, Simon (Simon.Green_at_EU.ALTRIA.COM)
Date: 07/22/04
- Previous message: Green, Simon: "Re: Upperbound param in LV"
- Maybe in reply to: Kumar, Praveen (cahoot): "Re: ??: Disks used by LV"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 22 Jul 2004 15:21:54 +0200 To: aix-l@Princeton.EDU
It's theoretically possible that LVM would choose to allocate partitions on
hdisk2 first, then hdisk1. This could get messy! Doing two extendlvs would
prevent that, but it's also possible to prevent it by specifying an
inter-volume allocation of "minimum", which will force LVM to allocate on
the existing disk(s) before extending onto another disk.
My preferred solution when disk placement is important is to use a map.
e.g.
hdisk1:400-537
hdisk2:1-100
Then... extendlv -m <map_file> lv_name 238
Your map_file can cover more PPs than you actually want, but not less. The
partitions will be used in the order in which they are listed. All of the
PPs listed must be unallocated, so if there were one odd partition used in
the middle of a range, you'd have to split it into two.
e.g.
hdisk2:1-40
hdisk2:42=101
If you're careful with your intra- and inter-volume allocation policies this
isn't usually necessary, but sometimes it's nice to be sure what's going on.
I've seen LVM do strange things when extending LVs from time to time. Use
of maps is ESPECIALLY important if you're mirroring, IMHO.
-- Simon Green Altria ITSC Europe Ltd AIX-L Archive at https://new-lists.princeton.edu/listserv/aix-l.html <https://new-lists.princeton.edu/listserv/aix-l.html> New to AIX? http://publib-b.boulder.ibm.com/redbooks.nsf/portals/UNIX <http://publib-b.boulder.ibm.com/redbooks.nsf/portals/UNIX> N.B. Unsolicited email from vendors will not be appreciated. Please post all follow-ups to the list. -----Original Message----- From: Kumar, Praveen (cahoot) [mailto:Praveen.Kumar@CAHOOT.COM] Sent: 22 July 2004 13:03 To: aix-l@Princeton.EDU Subject: Re: ??: Disks used by LV Ok do you want me to give both the hdisk numbers in one go. something like this extendlv lv_name <no of LP's> hdisk1 hdisk2.. isn't it? So this uses the available disk space on hdisk1 first and the for the remaining space it picks up from the next given disk. Right.
- Previous message: Green, Simon: "Re: Upperbound param in LV"
- Maybe in reply to: Kumar, Praveen (cahoot): "Re: ??: Disks used by LV"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
