Whoa, so on another server I just added a new disk dynamically
I have a script that does the vmcp link, dasd_configure, dasdfmt, fdasd,
pvcreate, and vgextend
Now the vgextend failed
Finished formatting the device.
Rereading the partition table... ok
reading volume label ..: VOL1
reading vtoc ..........: ok
auto-creating one partition for the whole disk...
writing volume label...
writing VTOC...
rereading partition table...
Physical volume "/dev/dasdp1" successfully created
Volume group "app" not found
Cannot process volume group app
vgextend failed with a return code of 5 trying to add 8006 to VG app
Leaving the PV /det/disk/by-path/ccw-0.0.8006-part1 unassigned to an VG
And now the server thinks the whole volume group disappeared
cdzea02a9919:~ # vgs
VG #PV #LV #SN Attr VSize VFree
app 6 5 0 wz--n- 56.19g 1.19g
system 3 6 0 wz--n- 20.62g 1.14g
cdzea02a9919:~ # pvs
PV VG Fmt Attr PSize PFree
/dev/dasdd1 system lvm2 a-- 6.88g 396.00m
/dev/dasdg1 system lvm2 a-- 6.88g 0
/dev/dasdh1 system lvm2 a-- 6.88g 768.00m
/dev/dasdi1 app lvm2 a-- 2.29g 1.19g
/dev/dasdj1 app lvm2 a-- 22.49g 0
/dev/dasdk1 app lvm2 a-- 22.49g 0
/dev/dasdl1 app lvm2 a-- 5.49g 0
/dev/dasdn1 app lvm2 a-- 1.71g 0
/dev/dasdo1 app lvm2 a-- 1.71g 0
/dev/dasdp1 lvm2 --- 4.12g 4.12g
cdzea02a9919:~ # vgdisplay app
Volume group "app" not found
Cannot process volume group app
cdzea02a9919:~ # vgextend app /dev/dasdp1
Volume group "app" not found
Cannot process volume group app
Given the timing in the logs it looks like it is trying a PV scan immediately
when the disk is varied on
Which is probably before or during the dasdfmt and confusing LVM terribly.
May 01 18:12:15 cdzea02a9919 kernel: crw_info : CRW reports slct=0, oflw=0,
chn=0, rsc=3, anc=1, erc=4, rsid=F
May 01 18:12:25 cdzea02a9919 kernel: dasd-eckd.401b68: 0.0.8006: A channel path
to the device has become operational
May 01 18:12:25 cdzea02a9919 kernel: dasd-eckd.2aa01a: 0.0.8006: New DASD
3390/0C (CU 3990/01) with 6000 cylinders, 15 heads, 224
May 01 18:12:25 cdzea02a9919 kernel: dasd-eckd.412b53: 0.0.8006: DASD with 4
KB/block, 4320000 KB total size, 48 KB/track, compati
May 01 18:12:25 cdzea02a9919 kernel: dasdp:VOL1/ 0X8002: dasdp1
May 01 18:12:25 cdzea02a9919 kernel: dasdp: p1 size 9613248 extends beyond EOD,
truncated
May 01 18:12:25 cdzea02a9919 systemd[1]: Starting LVM2 PV scan on device
94:61...
May 01 18:12:25 cdzea02a9919 systemd[1]: Started LVM2 PV scan on device 94:61.
May 01 18:12:35 cdzea02a9919 kernel: dasd-eckd.b3193d: 0.0.8006: An error
occurred in the DASD device driver, reason=09
May 01 18:12:35 cdzea02a9919 kernel: dasd(eckd): I/O status report for device
0.0.8006:
dasd(eckd): in req: 000000007d437ed8 CC:00
FC:04 AC:00 SC:17 DS:0E CS:00 RC:0
dasd(eckd): device 0.0.8006: Failing CCW:
000000007d437fe8
dasd(eckd): Sense(hex) 0- 7: 80 00 00 00
00 00 00 0f
dasd(eckd): Sense(hex) 8-15: ef 05 00 00
00 00 00 00
dasd(eckd): Sense(hex) 16-23: 00 00 00 00
3a 00 0f 00
dasd(eckd): Sense(hex) 24-31: 00 00 60 e0
00 00 00 00
dasd(eckd): 24 Byte: 0 MSG f, no MSGb to
SYSOP
May 01 18:12:35 cdzea02a9919 kernel: dasd(eckd): Related CP in req:
000000007d437ed8
dasd(eckd): CCW 000000007d437fe0: 2760000C
7D437FF0 DAT: 18000000 46171c00 00000000
dasd(eckd): CCW 000000007d437fe8: 3E20401A
513C0000 DAT: 00000000 00000000 00000000 0000000
May 01 18:12:35 cdzea02a9919 systemd-udevd[1045]: Network interface NamePolicy=
disabled by default.
May 01 18:12:36 cdzea02a9919 systemd[1]: Started /sbin/lvm pvscan --cache 94:61.
May 01 18:12:36 cdzea02a9919 systemd[1]: Stopping LVM2 PV scan on device
94:61...
May 01 18:12:36 cdzea02a9919 lvm[38587]: Device 94:61 not found. Cleared from
lvmetad cache.
May 01 18:12:36 cdzea02a9919 lvm[38590]: Device 94:61 not found. Cleared from
lvmetad cache.
May 01 18:12:36 cdzea02a9919 systemd[1]: Stopped LVM2 PV scan on device 94:61.
So maybe LVM2 needs to hold off in SLES 12 SP2? How?
And yes, its entirely possible the minidisk had stuff on it before which is why
we always dasdfmt first.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
