This is a discussion on problem with "mirrorvg -m" within the AIX Operating System forums, part of the Unix Operating Systems category; --> Hello, I'd like to mirrovg and have an exact PPs location on second copy. Please tell me what do ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, I'd like to mirrovg and have an exact PPs location on second copy. Please tell me what do I do wrong that mirrovg fails. regards, A. root@n7p21r3 /dev/pts/1 / # lspv hdisk0 007810c52b349455 rootvg active hdisk1 007810c5514fd582 rootvg active hssaSR1D9-9 007810c53077c413 datavg active hssaSR1D9-10 007810c5c077ce65 datavg active hssaSR1D9-11 007810c5c073c0a3 datavg active hssaSR1D9-12 007810c5c077c3fa datavg active hssaSR1D9-13 0038412a6043b4fe datavg active hssaSR1D9-16 0038412a6048e46d datavg active hssaSR2D9-9 0028314f778a9483 datavg active hssaSR2D9-10 0028314f7784a42a datavg active hssaSR2D9-11 0028314f778aaad8 datavg active hssaSR2D9-12 0028314f778a514e datavg active hssaSR2D9-13 0028314f778ab5b2 datavg active hssaSR2D9-16 0038412a752ab504 datavg active root@n7p21r3 /dev/pts/1 / # lsvg -p datavg datavg: PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION hssaSR1D9-9 active 543 478 108..109..44..108..109 hssaSR1D9-10 active 543 479 109..109..44..108..109 hssaSR1D9-11 active 543 479 109..109..44..108..109 hssaSR1D9-12 active 543 390 109..36..28..108..109 hssaSR1D9-13 active 271 260 55..54..43..54..54 hssaSR1D9-16 active 271 144 14..14..08..54..54 hssaSR2D9-9 active 543 543 109..109..108..108..109 hssaSR2D9-10 active 543 543 109..109..108..108..109 hssaSR2D9-11 active 543 543 109..109..108..108..109 hssaSR2D9-12 active 543 543 109..109..108..108..109 hssaSR2D9-13 active 271 271 55..54..54..54..54 hssaSR2D9-16 active 271 271 55..54..54..54..54 root@n7p21r3 /dev/pts/1 / # lsdev -Cc pdisk pssaSR1D9-10 Available 3L-08-R1D9-10-P SSA160 Physical Disk Drive pssaSR1D9-11 Available 3L-08-R1D9-11-P SSA160 Physical Disk Drive pssaSR1D9-12 Available 3L-08-R1D9-12-P SSA160 Physical Disk Drive pssaSR1D9-13 Available 3L-08-R1D9-13-P SSA160 Physical Disk Drive pssaSR1D9-16 Available 3L-08-R1D9-16-P SSA160 Physical Disk Drive pssaSR1D9-9 Available 3L-08-R1D9-09-P SSA160 Physical Disk Drive pssaSR2D9-10 Available 3H-08-R2D9-10-P SSA160 Physical Disk Drive pssaSR2D9-11 Available 3H-08-R2D9-11-P SSA160 Physical Disk Drive pssaSR2D9-12 Available 3H-08-R2D9-12-P SSA160 Physical Disk Drive pssaSR2D9-13 Available 3L-08-R2D9-13-P SSA160 Physical Disk Drive pssaSR2D9-16 Available 3L-08-R2D9-16-P SSA160 Physical Disk Drive pssaSR2D9-9 Available 3H-08-R2D9-09-P SSA160 Physical Disk Drive root@n7p21r3 /dev/pts/1 / # lsvg -o datavg rootvg root@n7p21r3 /dev/pts/1 / # mirrorvg -m datavg hssaSR2D9-9 hssaSR2D9-10 hssaSR2D9-11 hssaSR2D9-12 hssaSR2D9-13 hssaSR2D9-16 0516-418 allocp: Illegal data on standard input map line 1. 0516-1199 mirrorvg: Failed to create logical partition copies for logical volume jfslog1_lv. 0516-1200 mirrorvg: Failed to mirror the volume group. root@n7p21r3 /dev/pts/1 / # |
| |||
| "Andy" <gk15374@yahoo.com> schrieb im Newsbeitrag news:e01e9fdb.0309050257.dddafaa@posting.google.co m... > Hello, > I'd like to mirrovg and have an exact PPs location on second copy. > Please tell me what do I do wrong that mirrovg fails. > > regards, > A. > > > root@n7p21r3 /dev/pts/1 / > # lspv > hdisk0 007810c52b349455 rootvg > active > hdisk1 007810c5514fd582 rootvg > active > hssaSR1D9-9 007810c53077c413 datavg > active > hssaSR1D9-10 007810c5c077ce65 datavg > active > hssaSR1D9-11 007810c5c073c0a3 datavg > active > hssaSR1D9-12 007810c5c077c3fa datavg > active > hssaSR1D9-13 0038412a6043b4fe datavg > active > hssaSR1D9-16 0038412a6048e46d datavg > active > hssaSR2D9-9 0028314f778a9483 datavg > active > hssaSR2D9-10 0028314f7784a42a datavg > active > hssaSR2D9-11 0028314f778aaad8 datavg > active > hssaSR2D9-12 0028314f778a514e datavg > active > hssaSR2D9-13 0028314f778ab5b2 datavg > active > hssaSR2D9-16 0038412a752ab504 datavg > active > root@n7p21r3 /dev/pts/1 / > # lsvg -p datavg > datavg: > PV_NAME PV STATE TOTAL PPs FREE PPs FREE > DISTRIBUTION > hssaSR1D9-9 active 543 478 > 108..109..44..108..109 > hssaSR1D9-10 active 543 479 > 109..109..44..108..109 > hssaSR1D9-11 active 543 479 > 109..109..44..108..109 > hssaSR1D9-12 active 543 390 > 109..36..28..108..109 > hssaSR1D9-13 active 271 260 > 55..54..43..54..54 > hssaSR1D9-16 active 271 144 > 14..14..08..54..54 > hssaSR2D9-9 active 543 543 > 109..109..108..108..109 > hssaSR2D9-10 active 543 543 > 109..109..108..108..109 > hssaSR2D9-11 active 543 543 > 109..109..108..108..109 > hssaSR2D9-12 active 543 543 > 109..109..108..108..109 > hssaSR2D9-13 active 271 271 > 55..54..54..54..54 > hssaSR2D9-16 active 271 271 > 55..54..54..54..54 > root@n7p21r3 /dev/pts/1 / > # lsdev -Cc pdisk > pssaSR1D9-10 Available 3L-08-R1D9-10-P SSA160 Physical Disk Drive > pssaSR1D9-11 Available 3L-08-R1D9-11-P SSA160 Physical Disk Drive > pssaSR1D9-12 Available 3L-08-R1D9-12-P SSA160 Physical Disk Drive > pssaSR1D9-13 Available 3L-08-R1D9-13-P SSA160 Physical Disk Drive > pssaSR1D9-16 Available 3L-08-R1D9-16-P SSA160 Physical Disk Drive > pssaSR1D9-9 Available 3L-08-R1D9-09-P SSA160 Physical Disk Drive > pssaSR2D9-10 Available 3H-08-R2D9-10-P SSA160 Physical Disk Drive > pssaSR2D9-11 Available 3H-08-R2D9-11-P SSA160 Physical Disk Drive > pssaSR2D9-12 Available 3H-08-R2D9-12-P SSA160 Physical Disk Drive > pssaSR2D9-13 Available 3L-08-R2D9-13-P SSA160 Physical Disk Drive > pssaSR2D9-16 Available 3L-08-R2D9-16-P SSA160 Physical Disk Drive > pssaSR2D9-9 Available 3H-08-R2D9-09-P SSA160 Physical Disk Drive > root@n7p21r3 /dev/pts/1 / > # lsvg -o > datavg > rootvg > root@n7p21r3 /dev/pts/1 / > # mirrorvg -m datavg hssaSR2D9-9 hssaSR2D9-10 hssaSR2D9-11 > hssaSR2D9-12 hssaSR2D9-13 hssaSR2D9-16 > 0516-418 allocp: Illegal data on standard input map line 1. > 0516-1199 mirrorvg: Failed to create logical partition copies > for logical volume jfslog1_lv. > 0516-1200 mirrorvg: Failed to mirror the volume group. > root@n7p21r3 /dev/pts/1 / > # Hallo Andy, this error message looks like the error message mklv generates if it is given a wrong map file. E.g. mklv expects a map file in the format: hdisk0:10-23 for UNused partitions! For used partitions the output would look like: hdisk0:10 burpfslv:8 (for the eigth lp of the burpfslv on the hdisk0 placed at pp 10). However, this would be the wrong format for mklv (which is used by mirrorvg). Thus I would guess that there is some logival volume (e.g.the jfslog1_lv in your case) on your target disks already. If this was the true, just clear the target disks from any lv or fs information and restart the mirrorvg. regards, Andreas |
| |||
| Originally posted by Andreas Schulze > "Andy" <gk15374@yahoo.com> schrieb im Newsbeitrag > news:e01e9fdb.0309050257.dddafaa@posting.google.co m"]news:e01e9- > fdb.0309050257.dddafaa@posting.google.com[/url]... > > Hello, > > I'd like to mirrovg and have an exact PPs location on second > copy. > > Please tell me what do I do wrong that mirrovg fails. > > regards, > > A. > > root@n7p21r3 /dev/pts/1 / > > # lspv > > hdisk0 007810c52b349455 rootvg > > active > > hdisk1 007810c5514fd582 rootvg > > active > > hssaSR1D9-9 007810c53077c413 datavg > > active > > hssaSR1D9-10 007810c5c077ce65 datavg > > active > > hssaSR1D9-11 007810c5c073c0a3 datavg > > active > > hssaSR1D9-12 007810c5c077c3fa datavg > > active > > hssaSR1D9-13 0038412a6043b4fe datavg > > active > > hssaSR1D9-16 0038412a6048e46d datavg > > active > > hssaSR2D9-9 0028314f778a9483 datavg > > active > > hssaSR2D9-10 0028314f7784a42a datavg > > active > > hssaSR2D9-11 0028314f778aaad8 datavg > > active > > hssaSR2D9-12 0028314f778a514e datavg > > active > > hssaSR2D9-13 0028314f778ab5b2 datavg > > active > > hssaSR2D9-16 0038412a752ab504 datavg > > active > > root@n7p21r3 /dev/pts/1 / > > # lsvg -p datavg > > datavg: > > PV_NAME PV STATE TOTAL PPs FREE PPs > FREE > > DISTRIBUTION > > hssaSR1D9-9 active 543 478 > > 108..109..44..108..109 > > hssaSR1D9-10 active 543 479 > > 109..109..44..108..109 > > hssaSR1D9-11 active 543 479 > > 109..109..44..108..109 > > hssaSR1D9-12 active 543 390 > > 109..36..28..108..109 > > hssaSR1D9-13 active 271 260 > > 55..54..43..54..54 > > hssaSR1D9-16 active 271 144 > > 14..14..08..54..54 > > hssaSR2D9-9 active 543 543 > > 109..109..108..108..109 > > hssaSR2D9-10 active 543 543 > > 109..109..108..108..109 > > hssaSR2D9-11 active 543 543 > > 109..109..108..108..109 > > hssaSR2D9-12 active 543 543 > > 109..109..108..108..109 > > hssaSR2D9-13 active 271 271 > > 55..54..54..54..54 > > hssaSR2D9-16 active 271 271 > > 55..54..54..54..54 > > root@n7p21r3 /dev/pts/1 / > > # lsdev -Cc pdisk > > pssaSR1D9-10 Available 3L-08-R1D9-10-P SSA160 Physical Disk > Drive > > pssaSR1D9-11 Available 3L-08-R1D9-11-P SSA160 Physical Disk > Drive > > pssaSR1D9-12 Available 3L-08-R1D9-12-P SSA160 Physical Disk > Drive > > pssaSR1D9-13 Available 3L-08-R1D9-13-P SSA160 Physical Disk > Drive > > pssaSR1D9-16 Available 3L-08-R1D9-16-P SSA160 Physical Disk > Drive > > pssaSR1D9-9 Available 3L-08-R1D9-09-P SSA160 Physical Disk > Drive > > pssaSR2D9-10 Available 3H-08-R2D9-10-P SSA160 Physical Disk > Drive > > pssaSR2D9-11 Available 3H-08-R2D9-11-P SSA160 Physical Disk > Drive > > pssaSR2D9-12 Available 3H-08-R2D9-12-P SSA160 Physical Disk > Drive > > pssaSR2D9-13 Available 3L-08-R2D9-13-P SSA160 Physical Disk > Drive > > pssaSR2D9-16 Available 3L-08-R2D9-16-P SSA160 Physical Disk > Drive > > pssaSR2D9-9 Available 3H-08-R2D9-09-P SSA160 Physical Disk > Drive > > root@n7p21r3 /dev/pts/1 / > > # lsvg -o > > datavg > > rootvg > > root@n7p21r3 /dev/pts/1 / > > # mirrorvg -m datavg hssaSR2D9-9 hssaSR2D9-10 hssaSR2D9-11 > > hssaSR2D9-12 hssaSR2D9-13 hssaSR2D9-16 > > 0516-418 allocp: Illegal data on standard input map line 1. > > 0516-1199 mirrorvg: Failed to create logical partition > copies > > for logical volume jfslog1_lv. > > 0516-1200 mirrorvg: Failed to mirror the volume group. > > root@n7p21r3 /dev/pts/1 / > > # > > Hallo Andy, > > this error message looks like the error message mklv generates > if it is > given a wrong map file. E.g. mklv expects a map file in the format: > hdisk0:10-23 > for UNused partitions! > For used partitions the output would look like: > hdisk0:10 burpfslv:8 > (for the eigth lp of the burpfslv on the hdisk0 placed at pp 10). > However, > this would be the wrong format for mklv (which is used by mirrorvg). > > Thus I would guess that there is some logival volume (e.g.the > jfslog1_lv in > your case) on your target disks already. If this was the true, > just clear > the target disks from any lv or fs information and restart the > mirrorvg. > > regards, > Andreas Hi Andreas, The disks I would like to use for mirror copy are brand new and empty (ne LV exists - I'd added them today to datavg). They are identical as disks in the only copy I have now. BTW: when I do "mklvcopy jfslog1_lv 2 hssaSR2D9-9" it is completed successfuly but I would like to run mirrovg to do it for all LVs in the VG). regards, Andy. -- Posted via http://dbforums.com |
| |||
| "Andy" <gk15374@yahoo.com> schrieb im Newsbeitrag news:e01e9fdb.0309050257.dddafaa@posting.google.co m... > Hello, > I'd like to mirrovg and have an exact PPs location on second copy. > Please tell me what do I do wrong that mirrovg fails. > > regards, > A. > > > root@n7p21r3 /dev/pts/1 / > # lspv > hdisk0 007810c52b349455 rootvg > active > hdisk1 007810c5514fd582 rootvg > active > hssaSR1D9-9 007810c53077c413 datavg > active > hssaSR1D9-10 007810c5c077ce65 datavg > active > hssaSR1D9-11 007810c5c073c0a3 datavg > active > hssaSR1D9-12 007810c5c077c3fa datavg > active > hssaSR1D9-13 0038412a6043b4fe datavg > active > hssaSR1D9-16 0038412a6048e46d datavg > active > hssaSR2D9-9 0028314f778a9483 datavg > active > hssaSR2D9-10 0028314f7784a42a datavg > active > hssaSR2D9-11 0028314f778aaad8 datavg > active > hssaSR2D9-12 0028314f778a514e datavg > active > hssaSR2D9-13 0028314f778ab5b2 datavg > active > hssaSR2D9-16 0038412a752ab504 datavg > active > root@n7p21r3 /dev/pts/1 / > # lsvg -p datavg > datavg: > PV_NAME PV STATE TOTAL PPs FREE PPs FREE > DISTRIBUTION > hssaSR1D9-9 active 543 478 > 108..109..44..108..109 > hssaSR1D9-10 active 543 479 > 109..109..44..108..109 > hssaSR1D9-11 active 543 479 > 109..109..44..108..109 > hssaSR1D9-12 active 543 390 > 109..36..28..108..109 > hssaSR1D9-13 active 271 260 > 55..54..43..54..54 > hssaSR1D9-16 active 271 144 > 14..14..08..54..54 > hssaSR2D9-9 active 543 543 > 109..109..108..108..109 > hssaSR2D9-10 active 543 543 > 109..109..108..108..109 > hssaSR2D9-11 active 543 543 > 109..109..108..108..109 > hssaSR2D9-12 active 543 543 > 109..109..108..108..109 > hssaSR2D9-13 active 271 271 > 55..54..54..54..54 > hssaSR2D9-16 active 271 271 > 55..54..54..54..54 > root@n7p21r3 /dev/pts/1 / > # lsdev -Cc pdisk > pssaSR1D9-10 Available 3L-08-R1D9-10-P SSA160 Physical Disk Drive > pssaSR1D9-11 Available 3L-08-R1D9-11-P SSA160 Physical Disk Drive > pssaSR1D9-12 Available 3L-08-R1D9-12-P SSA160 Physical Disk Drive > pssaSR1D9-13 Available 3L-08-R1D9-13-P SSA160 Physical Disk Drive > pssaSR1D9-16 Available 3L-08-R1D9-16-P SSA160 Physical Disk Drive > pssaSR1D9-9 Available 3L-08-R1D9-09-P SSA160 Physical Disk Drive > pssaSR2D9-10 Available 3H-08-R2D9-10-P SSA160 Physical Disk Drive > pssaSR2D9-11 Available 3H-08-R2D9-11-P SSA160 Physical Disk Drive > pssaSR2D9-12 Available 3H-08-R2D9-12-P SSA160 Physical Disk Drive > pssaSR2D9-13 Available 3L-08-R2D9-13-P SSA160 Physical Disk Drive > pssaSR2D9-16 Available 3L-08-R2D9-16-P SSA160 Physical Disk Drive > pssaSR2D9-9 Available 3H-08-R2D9-09-P SSA160 Physical Disk Drive > root@n7p21r3 /dev/pts/1 / > # lsvg -o > datavg > rootvg > root@n7p21r3 /dev/pts/1 / > # mirrorvg -m datavg hssaSR2D9-9 hssaSR2D9-10 hssaSR2D9-11 > hssaSR2D9-12 hssaSR2D9-13 hssaSR2D9-16 > 0516-418 allocp: Illegal data on standard input map line 1. > 0516-1199 mirrorvg: Failed to create logical partition copies > for logical volume jfslog1_lv. > 0516-1200 mirrorvg: Failed to mirror the volume group. > root@n7p21r3 /dev/pts/1 / > # 1) Why do you have so uncommon hdisk names ? Did you messed around with the hdisk names ? For debugging: I assume that your new "hdisks" are right now empty and that the "mirrorvg" does not like the "-" in your hdisk names. So: * backup up "/usr/sbin/mirrorvg * Open the file /usr/sbin/mirrorvg with "vi" and insert a "set -x" in every function and in the second line * Execute mirrorvg -m datavg .............. HTH Hajo CATE AIX/RS6000 have no Hopefully you have not messed around with the I really do not know |
| ||||
| > 1) Why do you have so uncommon hdisk names ? Did you messed around with the > hdisk names ? Names are OK. I renamed default hdisk naming with simple script to easily determine the SSA disk location (each mirror copy's disks are located in different SSA rack and drawer - different buildings). > > For debugging: > I assume that your new "hdisks" are right now empty and that the "mirrorvg" > does not like the "-" in your hdisk names. I don't think this is the reason - I don't remember the problem on 4.3.3 systems where I have the same disk naming convention with "-") BTW: I it will be not possible to do it with "mirrorvg" I'll do it with "mklvcopy" which works properly) > So: > * backup up "/usr/sbin/mirrorvg > * Open the file /usr/sbin/mirrorvg with "vi" and insert a "set -x" in every > function and in the second line > * Execute mirrorvg -m datavg .............. First I try to do it without modifying the "mirorvg" - just "set -x" for session I run mirrorvg.. regards, Andy. > > HTH > Hajo > > CATE AIX/RS6000 > > have no > Hopefully you have not messed around with the I really do not know |