SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
01-04-2008, 09:41 PM
| ||||
| ||||
 vpath and hdisk confusion Dear All, Hope someone could suggest what can be done here... the lsess output shows that for LSS 10, I have 6 hdisks. But should only have 4. If i do lsattr -El vpath0, it says hdisk4 and hdisk28, But there's no hdisk28 in the system. lsdev -C |grep hdisk28 -> nothing. lscfg -vl hdisk28 -> also nothing. I've tried running cfgmgr, but it still remains the same. I've not tried to reboot the system though. Its our production server, and can't be shutdown so easily. Can anything be done for this? I'm asking IBM as well.. but they're the ones to set it up this way  .lsess output Disk Location LUN SN Type Size LSS Vol Rank C/A S Connection ------ ------------ -------- ------------ ---- --- --- ---- --- - ----------- hdisk4 2D-08-01[FC] 00014364 IBM 2105-F20 26.3 10 0 1000 01 Y R1-B4-H1-ZA hdisk5 2D-08-01[FC] 00114364 IBM 2105-F20 26.3 10 1 1000 01 Y R1-B4-H1-ZA hdisk6 2D-08-01[FC] 10014364 IBM 2105-F20 26.3 11 0 1100 11 Y R1-B4-H1-ZA hdisk7 2D-08-01[FC] 10114364 IBM 2105-F20 26.3 11 1 1100 11 Y R1-B4-H1-ZA hdisk8 2D-08-01[FC] 20014364 IBM 2105-F20 26.3 12 0 1200 02 Y R1-B4-H1-ZA hdisk9 2D-08-01[FC] 20114364 IBM 2105-F20 26.3 12 1 1200 02 Y R1-B4-H1-ZA hdisk10 17-08-01[FC] 30014364 IBM 2105-F20 26.3 13 0 1300 12 Y R1-B1-H1-ZA hdisk11 17-08-01[FC] 30114364 IBM 2105-F20 26.3 13 1 1300 12 Y R1-B1-H1-ZA hdisk12 17-08-01[FC] 40014364 IBM 2105-F20 26.3 14 0 1400 03 Y R1-B1-H1-ZA hdisk13 17-08-01[FC] 40114364 IBM 2105-F20 26.3 14 1 1400 03 Y R1-B1-H1-ZA hdisk14 17-08-01[FC] 50014364 IBM 2105-F20 26.3 15 0 1500 13 Y R1-B1-H1-ZA hdisk15 17-08-01[FC] 50114364 IBM 2105-F20 26.3 15 1 1500 13 Y R1-B1-H1-ZA hdisk16 17-08-01[FC] 00014364 IBM 2105-F20 26.3 10 0 1000 01 Y R1-B1-H1-ZA hdisk17 17-08-01[FC] 00114364 IBM 2105-F20 26.3 10 1 1000 01 Y R1-B1-H1-ZA hdisk18 17-08-01[FC] 10014364 IBM 2105-F20 26.3 11 0 1100 11 Y R1-B1-H1-ZA hdisk19 17-08-01[FC] 20014364 IBM 2105-F20 26.3 12 0 1200 02 Y R1-B1-H1-ZA hdisk20 2D-08-01[FC] 20014364 IBM 2105-F20 26.3 12 0 1200 02 Y R1-B4-H1-ZA hdisk21 2D-08-01[FC] 20114364 IBM 2105-F20 26.3 12 1 1200 02 Y R1-B4-H1-ZA hdisk22 2D-08-01[FC] 30014364 IBM 2105-F20 26.3 13 0 1300 12 Y R1-B4-H1-ZA hdisk23 2D-08-01[FC] 30114364 IBM 2105-F20 26.3 13 1 1300 12 Y R1-B4-H1-ZA hdisk24 2D-08-01[FC] 40014364 IBM 2105-F20 26.3 14 0 1400 03 Y R1-B4-H1-ZA hdisk25 2D-08-01[FC] 40114364 IBM 2105-F20 26.3 14 1 1400 03 Y R1-B4-H1-ZA hdisk26 2D-08-01[FC] 50014364 IBM 2105-F20 26.3 15 0 1500 13 Y R1-B4-H1-ZA hdisk27 2D-08-01[FC] 50114364 IBM 2105-F20 26.3 15 1 1500 13 Y R1-B4-H1-ZA hdisk28 17-08-01[FC] 00014364 IBM 2105-F20 26.3 10 0 1000 01 Y R1-B1-H1-ZA hdisk29 17-08-01[FC] 00114364 IBM 2105-F20 26.3 10 1 1000 01 Y R1-B1-H1-ZA hdisk30 17-08-01[FC] 10014364 IBM 2105-F20 26.3 11 0 1100 11 Y R1-B1-H1-ZA hdisk31 17-08-01[FC] 10114364 IBM 2105-F20 26.3 11 1 1100 11 Y R1-B1-H1-ZA hdisk32 17-08-01[FC] 20014364 IBM 2105-F20 26.3 12 0 1200 02 Y R1-B1-H1-ZA hdisk33 17-08-01[FC] 20114364 IBM 2105-F20 26.3 12 1 1200 02 Y R1-B1-H1-ZA      |
|
01-04-2008, 09:42 PM
| |||
| |||
| Re: vpath and hdisk confusion g1303@yahoo.com (Ping Ai) wrote in message news:<c5df9c1f.0402190159.137af5f5@posting.google. com>... > Dear All, > > Hope someone could suggest what can be done here... the lsess output > shows that for LSS 10, I have 6 hdisks. But should only have 4. > If i do lsattr -El vpath0, it says hdisk4 and hdisk28, But there's no > hdisk28 in the system. lsdev -C |grep hdisk28 -> nothing. lscfg -vl > hdisk28 -> also nothing. I've tried running cfgmgr, but it still > remains the same. I've not tried to reboot the system though. Its our > production server, and can't be shutdown so easily. Can anything be > done for this? > I'm asking IBM as well.. but they're the ones to set it up this way > .> Probably there used to be an hdisk28 but now it's gone, though a bit odd that it doesn't show up at all in lsdev (I would expect it to be defined). If you have a new version of SDD, I think you can add and remove paths (i.e. hdisks from a vpath) but I'm not sure you can do this with the filesystems mounted. The best thing to do is probably to get an outage, delete all the vpaths and hdisks and reconfigure them from scratch. You can do this easily and you won't need to reboot or lose the volume group information. rmdev -dl dpo -R rmdev -dl hdiskx (for every ESS hdisk) cfgmgr -vl fcs0 (assuming you connect over fibre, repeat for each adapter) cfallvpath hd2vp <VG name> If you have a version of SDD older that 1.4 (latest is 1.5.something) or an old version of the ESS device driver, this would also be a good opportunity to update them. Iain. |
|
01-04-2008, 09:42 PM
| |||
| |||
| Re: vpath and hdisk confusion g1303@yahoo.com (Ping Ai) wrote in message news:<c5df9c1f.0402190159.137af5f5@posting.google. com>... > Dear All, > > Hope someone could suggest what can be done here... the lsess output > shows that for LSS 10, I have 6 hdisks. But should only have 4. > If i do lsattr -El vpath0, it says hdisk4 and hdisk28, But there's no > hdisk28 in the system. lsdev -C |grep hdisk28 -> nothing. lscfg -vl > hdisk28 -> also nothing. I've tried running cfgmgr, but it still > remains the same. I've not tried to reboot the system though. Its our > production server, and can't be shutdown so easily. Can anything be > done for this? > I'm asking IBM as well.. but they're the ones to set it up this way > .> > looks like you have some corruption... you may need to drop the vpaths, sort out the hdisk issues and redefine your vpaths.. this will require that all i/o across the vpaths is stopped, so an outage will be required. the user guide is here... look under chapter 2 configuring/unconfiguring SDD http://www-1.ibm.com/support/docview...S7000303&aid=1 HTH Mark Taylor |
|
01-04-2008, 09:42 PM
| |||
| |||
| Re: vpath and hdisk confusion g1303@yahoo.com (Ping Ai) wrote in message news:<c5df9c1f.0402190159.137af5f5@posting.google. com>... > Dear All, > > Hope someone could suggest what can be done here... the lsess output > shows that for LSS 10, I have 6 hdisks. But should only have 4. > If i do lsattr -El vpath0, it says hdisk4 and hdisk28, But there's no > hdisk28 in the system. lsdev -C |grep hdisk28 -> nothing. lscfg -vl > hdisk28 -> also nothing. I've tried running cfgmgr, but it still > remains the same. I've not tried to reboot the system though. Its our > production server, and can't be shutdown so easily. Can anything be > done for this? > I'm asking IBM as well.. but they're the ones to set it up this way > .> > > lsess output > > Disk Location LUN SN Type Size LSS Vol > Rank C/A S Connection > ------ ------------ -------- ------------ ---- --- --- > ---- --- - ----------- > hdisk4 2D-08-01[FC] 00014364 IBM 2105-F20 26.3 10 0 > 1000 01 Y R1-B4-H1-ZA > hdisk5 2D-08-01[FC] 00114364 IBM 2105-F20 26.3 10 1 > 1000 01 Y R1-B4-H1-ZA > hdisk6 2D-08-01[FC] 10014364 IBM 2105-F20 26.3 11 0 > 1100 11 Y R1-B4-H1-ZA > hdisk7 2D-08-01[FC] 10114364 IBM 2105-F20 26.3 11 1 > 1100 11 Y R1-B4-H1-ZA > hdisk8 2D-08-01[FC] 20014364 IBM 2105-F20 26.3 12 0 > 1200 02 Y R1-B4-H1-ZA > hdisk9 2D-08-01[FC] 20114364 IBM 2105-F20 26.3 12 1 > 1200 02 Y R1-B4-H1-ZA > hdisk10 17-08-01[FC] 30014364 IBM 2105-F20 26.3 13 0 > 1300 12 Y R1-B1-H1-ZA > hdisk11 17-08-01[FC] 30114364 IBM 2105-F20 26.3 13 1 > 1300 12 Y R1-B1-H1-ZA > hdisk12 17-08-01[FC] 40014364 IBM 2105-F20 26.3 14 0 > 1400 03 Y R1-B1-H1-ZA > hdisk13 17-08-01[FC] 40114364 IBM 2105-F20 26.3 14 1 > 1400 03 Y R1-B1-H1-ZA > hdisk14 17-08-01[FC] 50014364 IBM 2105-F20 26.3 15 0 > 1500 13 Y R1-B1-H1-ZA > hdisk15 17-08-01[FC] 50114364 IBM 2105-F20 26.3 15 1 > 1500 13 Y R1-B1-H1-ZA > hdisk16 17-08-01[FC] 00014364 IBM 2105-F20 26.3 10 0 > 1000 01 Y R1-B1-H1-ZA > hdisk17 17-08-01[FC] 00114364 IBM 2105-F20 26.3 10 1 > 1000 01 Y R1-B1-H1-ZA > hdisk18 17-08-01[FC] 10014364 IBM 2105-F20 26.3 11 0 > 1100 11 Y R1-B1-H1-ZA > hdisk19 17-08-01[FC] 20014364 IBM 2105-F20 26.3 12 0 > 1200 02 Y R1-B1-H1-ZA > hdisk20 2D-08-01[FC] 20014364 IBM 2105-F20 26.3 12 0 > 1200 02 Y R1-B4-H1-ZA > hdisk21 2D-08-01[FC] 20114364 IBM 2105-F20 26.3 12 1 > 1200 02 Y R1-B4-H1-ZA > hdisk22 2D-08-01[FC] 30014364 IBM 2105-F20 26.3 13 0 > 1300 12 Y R1-B4-H1-ZA > hdisk23 2D-08-01[FC] 30114364 IBM 2105-F20 26.3 13 1 > 1300 12 Y R1-B4-H1-ZA > hdisk24 2D-08-01[FC] 40014364 IBM 2105-F20 26.3 14 0 > 1400 03 Y R1-B4-H1-ZA > hdisk25 2D-08-01[FC] 40114364 IBM 2105-F20 26.3 14 1 > 1400 03 Y R1-B4-H1-ZA > hdisk26 2D-08-01[FC] 50014364 IBM 2105-F20 26.3 15 0 > 1500 13 Y R1-B4-H1-ZA > hdisk27 2D-08-01[FC] 50114364 IBM 2105-F20 26.3 15 1 > 1500 13 Y R1-B4-H1-ZA > hdisk28 17-08-01[FC] 00014364 IBM 2105-F20 26.3 10 0 > 1000 01 Y R1-B1-H1-ZA > hdisk29 17-08-01[FC] 00114364 IBM 2105-F20 26.3 10 1 > 1000 01 Y R1-B1-H1-ZA > hdisk30 17-08-01[FC] 10014364 IBM 2105-F20 26.3 11 0 > 1100 11 Y R1-B1-H1-ZA > hdisk31 17-08-01[FC] 10114364 IBM 2105-F20 26.3 11 1 > 1100 11 Y R1-B1-H1-ZA > hdisk32 17-08-01[FC] 20014364 IBM 2105-F20 26.3 12 0 > 1200 02 Y R1-B1-H1-ZA > hdisk33 17-08-01[FC] 20114364 IBM 2105-F20 26.3 12 1 > 1200 02 Y R1-B1-H1-ZA Well, in actually, based on the LUN SN's, you only have 2 physical disks on that LSS (SN 001 and 000). 14364 is the SN of the Shark. BV |
|
01-04-2008, 09:42 PM
| |||
| |||
| Re: vpath and hdisk confusion g1303@yahoo.com (Ping Ai) wrote in message news:<c5df9c1f.0402190159.137af5f5@posting.google. com>... > Dear All, > > Hope someone could suggest what can be done here... the lsess output > shows that for LSS 10, I have 6 hdisks. But should only have 4. > If i do lsattr -El vpath0, it says hdisk4 and hdisk28, But there's no > hdisk28 in the system. lsdev -C |grep hdisk28 -> nothing. lscfg -vl > hdisk28 -> also nothing. I've tried running cfgmgr, but it still > remains the same. I've not tried to reboot the system though. Its our > production server, and can't be shutdown so easily. Can anything be > done for this? > I'm asking IBM as well.. but they're the ones to set it up this way > .> > > lsess output > > Disk Location LUN SN Type Size LSS Vol > Rank C/A S Connection > ------ ------------ -------- ------------ ---- --- --- > ---- --- - ----------- > hdisk4 2D-08-01[FC] 00014364 IBM 2105-F20 26.3 10 0 > 1000 01 Y R1-B4-H1-ZA > hdisk5 2D-08-01[FC] 00114364 IBM 2105-F20 26.3 10 1 > 1000 01 Y R1-B4-H1-ZA > hdisk6 2D-08-01[FC] 10014364 IBM 2105-F20 26.3 11 0 > 1100 11 Y R1-B4-H1-ZA > hdisk7 2D-08-01[FC] 10114364 IBM 2105-F20 26.3 11 1 > 1100 11 Y R1-B4-H1-ZA > hdisk8 2D-08-01[FC] 20014364 IBM 2105-F20 26.3 12 0 > 1200 02 Y R1-B4-H1-ZA > hdisk9 2D-08-01[FC] 20114364 IBM 2105-F20 26.3 12 1 > 1200 02 Y R1-B4-H1-ZA > hdisk10 17-08-01[FC] 30014364 IBM 2105-F20 26.3 13 0 > 1300 12 Y R1-B1-H1-ZA > hdisk11 17-08-01[FC] 30114364 IBM 2105-F20 26.3 13 1 > 1300 12 Y R1-B1-H1-ZA > hdisk12 17-08-01[FC] 40014364 IBM 2105-F20 26.3 14 0 > 1400 03 Y R1-B1-H1-ZA > hdisk13 17-08-01[FC] 40114364 IBM 2105-F20 26.3 14 1 > 1400 03 Y R1-B1-H1-ZA > hdisk14 17-08-01[FC] 50014364 IBM 2105-F20 26.3 15 0 > 1500 13 Y R1-B1-H1-ZA > hdisk15 17-08-01[FC] 50114364 IBM 2105-F20 26.3 15 1 > 1500 13 Y R1-B1-H1-ZA > hdisk16 17-08-01[FC] 00014364 IBM 2105-F20 26.3 10 0 > 1000 01 Y R1-B1-H1-ZA > hdisk17 17-08-01[FC] 00114364 IBM 2105-F20 26.3 10 1 > 1000 01 Y R1-B1-H1-ZA > hdisk18 17-08-01[FC] 10014364 IBM 2105-F20 26.3 11 0 > 1100 11 Y R1-B1-H1-ZA > hdisk19 17-08-01[FC] 20014364 IBM 2105-F20 26.3 12 0 > 1200 02 Y R1-B1-H1-ZA > hdisk20 2D-08-01[FC] 20014364 IBM 2105-F20 26.3 12 0 > 1200 02 Y R1-B4-H1-ZA > hdisk21 2D-08-01[FC] 20114364 IBM 2105-F20 26.3 12 1 > 1200 02 Y R1-B4-H1-ZA > hdisk22 2D-08-01[FC] 30014364 IBM 2105-F20 26.3 13 0 > 1300 12 Y R1-B4-H1-ZA > hdisk23 2D-08-01[FC] 30114364 IBM 2105-F20 26.3 13 1 > 1300 12 Y R1-B4-H1-ZA > hdisk24 2D-08-01[FC] 40014364 IBM 2105-F20 26.3 14 0 > 1400 03 Y R1-B4-H1-ZA > hdisk25 2D-08-01[FC] 40114364 IBM 2105-F20 26.3 14 1 > 1400 03 Y R1-B4-H1-ZA > hdisk26 2D-08-01[FC] 50014364 IBM 2105-F20 26.3 15 0 > 1500 13 Y R1-B4-H1-ZA > hdisk27 2D-08-01[FC] 50114364 IBM 2105-F20 26.3 15 1 > 1500 13 Y R1-B4-H1-ZA > hdisk28 17-08-01[FC] 00014364 IBM 2105-F20 26.3 10 0 > 1000 01 Y R1-B1-H1-ZA > hdisk29 17-08-01[FC] 00114364 IBM 2105-F20 26.3 10 1 > 1000 01 Y R1-B1-H1-ZA > hdisk30 17-08-01[FC] 10014364 IBM 2105-F20 26.3 11 0 > 1100 11 Y R1-B1-H1-ZA > hdisk31 17-08-01[FC] 10114364 IBM 2105-F20 26.3 11 1 > 1100 11 Y R1-B1-H1-ZA > hdisk32 17-08-01[FC] 20014364 IBM 2105-F20 26.3 12 0 > 1200 02 Y R1-B1-H1-ZA > hdisk33 17-08-01[FC] 20114364 IBM 2105-F20 26.3 12 1 > 1200 02 Y R1-B1-H1-ZA Also, use "ls2105". The lsess script I find to be less accurate. BV |
|
01-04-2008, 09:43 PM
| ||||
| ||||
| Re: vpath and hdisk confusion "Bill" <bverzal@komatsuna.com> wrote in message news:51157c68.0402190831.67fa1d00@posting.google.c om... > g1303@yahoo.com (Ping Ai) wrote in message news:<c5df9c1f.0402190159.137af5f5@posting.google. com>... > > Dear All, > > > > Hope someone could suggest what can be done here... the lsess output > > shows that for LSS 10, I have 6 hdisks. But should only have 4. > > If i do lsattr -El vpath0, it says hdisk4 and hdisk28, But there's no > > hdisk28 in the system. lsdev -C |grep hdisk28 -> nothing. lscfg -vl > > hdisk28 -> also nothing. I've tried running cfgmgr, but it still > > remains the same. I've not tried to reboot the system though. Its our > > production server, and can't be shutdown so easily. Can anything be > > done for this? > > I'm asking IBM as well.. but they're the ones to set it up this way > > .> > > > > > lsess output > > > > Disk Location LUN SN Type Size LSS Vol > > Rank C/A S Connection > > ------ ------------ -------- ------------ ---- --- --- > > ---- --- - ----------- > > hdisk4 2D-08-01[FC] 00014364 IBM 2105-F20 26.3 10 0 > > 1000 01 Y R1-B4-H1-ZA > > hdisk5 2D-08-01[FC] 00114364 IBM 2105-F20 26.3 10 1 > > 1000 01 Y R1-B4-H1-ZA > > hdisk6 2D-08-01[FC] 10014364 IBM 2105-F20 26.3 11 0 > > 1100 11 Y R1-B4-H1-ZA > > hdisk7 2D-08-01[FC] 10114364 IBM 2105-F20 26.3 11 1 > > 1100 11 Y R1-B4-H1-ZA > > hdisk8 2D-08-01[FC] 20014364 IBM 2105-F20 26.3 12 0 > > 1200 02 Y R1-B4-H1-ZA > > hdisk9 2D-08-01[FC] 20114364 IBM 2105-F20 26.3 12 1 > > 1200 02 Y R1-B4-H1-ZA > > hdisk10 17-08-01[FC] 30014364 IBM 2105-F20 26.3 13 0 > > 1300 12 Y R1-B1-H1-ZA > > hdisk11 17-08-01[FC] 30114364 IBM 2105-F20 26.3 13 1 > > 1300 12 Y R1-B1-H1-ZA > > hdisk12 17-08-01[FC] 40014364 IBM 2105-F20 26.3 14 0 > > 1400 03 Y R1-B1-H1-ZA > > hdisk13 17-08-01[FC] 40114364 IBM 2105-F20 26.3 14 1 > > 1400 03 Y R1-B1-H1-ZA > > hdisk14 17-08-01[FC] 50014364 IBM 2105-F20 26.3 15 0 > > 1500 13 Y R1-B1-H1-ZA > > hdisk15 17-08-01[FC] 50114364 IBM 2105-F20 26.3 15 1 > > 1500 13 Y R1-B1-H1-ZA > > hdisk16 17-08-01[FC] 00014364 IBM 2105-F20 26.3 10 0 > > 1000 01 Y R1-B1-H1-ZA > > hdisk17 17-08-01[FC] 00114364 IBM 2105-F20 26.3 10 1 > > 1000 01 Y R1-B1-H1-ZA > > hdisk18 17-08-01[FC] 10014364 IBM 2105-F20 26.3 11 0 > > 1100 11 Y R1-B1-H1-ZA > > hdisk19 17-08-01[FC] 20014364 IBM 2105-F20 26.3 12 0 > > 1200 02 Y R1-B1-H1-ZA > > hdisk20 2D-08-01[FC] 20014364 IBM 2105-F20 26.3 12 0 > > 1200 02 Y R1-B4-H1-ZA > > hdisk21 2D-08-01[FC] 20114364 IBM 2105-F20 26.3 12 1 > > 1200 02 Y R1-B4-H1-ZA > > hdisk22 2D-08-01[FC] 30014364 IBM 2105-F20 26.3 13 0 > > 1300 12 Y R1-B4-H1-ZA > > hdisk23 2D-08-01[FC] 30114364 IBM 2105-F20 26.3 13 1 > > 1300 12 Y R1-B4-H1-ZA > > hdisk24 2D-08-01[FC] 40014364 IBM 2105-F20 26.3 14 0 > > 1400 03 Y R1-B4-H1-ZA > > hdisk25 2D-08-01[FC] 40114364 IBM 2105-F20 26.3 14 1 > > 1400 03 Y R1-B4-H1-ZA > > hdisk26 2D-08-01[FC] 50014364 IBM 2105-F20 26.3 15 0 > > 1500 13 Y R1-B4-H1-ZA > > hdisk27 2D-08-01[FC] 50114364 IBM 2105-F20 26.3 15 1 > > 1500 13 Y R1-B4-H1-ZA > > hdisk28 17-08-01[FC] 00014364 IBM 2105-F20 26.3 10 0 > > 1000 01 Y R1-B1-H1-ZA > > hdisk29 17-08-01[FC] 00114364 IBM 2105-F20 26.3 10 1 > > 1000 01 Y R1-B1-H1-ZA > > hdisk30 17-08-01[FC] 10014364 IBM 2105-F20 26.3 11 0 > > 1100 11 Y R1-B1-H1-ZA > > hdisk31 17-08-01[FC] 10114364 IBM 2105-F20 26.3 11 1 > > 1100 11 Y R1-B1-H1-ZA > > hdisk32 17-08-01[FC] 20014364 IBM 2105-F20 26.3 12 0 > > 1200 02 Y R1-B1-H1-ZA > > hdisk33 17-08-01[FC] 20114364 IBM 2105-F20 26.3 12 1 > > 1200 02 Y R1-B1-H1-ZA > > Also, use "ls2105". The lsess script I find to be less accurate. > > BV The problem with the essutil commands is that it relies on a file in /var/adm/ras that is produced during bootup and if you have done any work since then, then commands such as lssdd, ls2105 etc will give you a PiT information, not current. You will have to use commands that give you info from current information like lsvpcfg or datapath query. I personally rely on datapath query device. lsattr -El on vpath is useful as well. Use the lscfg for currently available devices, along with lspv. If you have a problem after using these then revert volume group to hdisks and remove that vpaths affected and run cfgmgr on the dpo parent. Regards Paresh |
Linear Mode
