Looks like it.


[    1.384220] systemd[1]: Expecting device 
dev-disk-by\x2dpath-ccw\x2d0.0.ff02\x2dpart1.device...
[    1.384267] systemd[1]: Expecting device 
dev-disk-by\x2dpath-ccw\x2d0.0.ff00\x2dpart1.device...
[    1.384277] systemd[1]: Expecting device 
dev-mapper-system\x2dusr\x2d\x2dlv.device...
[    1.384288] systemd[1]: Expecting device 
dev-disk-by\x2dpath-ccw\x2d0.0.ff03\x2dpart1.device...
[    1.394629] SCSI subsystem initialized
[    1.615436] device-mapper: uevent: version 1.0.3
[    1.615475] device-mapper: ioctl: 4.26.0-ioctl (2013-08-15) initialised: 
dm-de...@redhat.com
[    2.168145] dasd-eckd.401b68: 0.0.0101: A channel path to the device has 
become operational
[    2.168435] dasd-fba.f36f2f: 0.0.ff00: New FBA DASD 9336/10 (CU 6310/80) 
with 244 MB and 512 B/blk
[    2.172878]  dasdb:(nonl) dasdb1
[    2.173857] dasd-eckd.2aa01a: 0.0.0101: New DASD 3390/0C (CU 3990/01) with 
1000 cylinders, 15 heads, 224 sectors
[    2.174467] dasd-fba.f36f2f: 0.0.ff01: New FBA DASD 9336/10 (CU 6310/80) 
with 488 MB and 512 B/blk
[    2.175182]  dasdc:(nonl) dasdc1
[    2.181184] dasd-eckd.412b53: 0.0.0101: DASD with 4 KB/block, 720000 KB 
total size, 48 KB/track, compatible disk layout
[    2.182056] dasd-fba.f36f2f: 0.0.ff02: New FBA DASD 9336/10 (CU 6310/80) 
with 976 MB and 512 B/blk
[    2.184822]  dasdd:(nonl) dasdd1
[    2.187338]  dasda:VOL1/  0X0201: dasda1
[    2.194562] dasd-fba.f36f2f: 0.0.ff03: New FBA DASD 9336/10 (CU 6310/80) 
with 1953 MB and 512 B/blk
[    2.199639]  dasde:(nonl) dasde1
[    2.206808] dasd-eckd.401b68: 0.0.0102: A channel path to the device has 
become operational
[    2.212005] dasd-eckd.2aa01a: 0.0.0102: New DASD 3390/0C (CU 3990/01) with 
17500 cylinders, 15 heads, 224 sectors
[    2.214644] dasd-eckd.412b53: 0.0.0102: DASD with 4 KB/block, 12600000 KB 
total size, 48 KB/track, compatible disk layout
[    2.221983]  dasdf:VOL1/  0X0102: dasdf1
[    2.236315] dasd-eckd.401b68: 0.0.0103: A channel path to the device has 
become operational
[    2.237607] dasd-eckd.2aa01a: 0.0.0103: New DASD 3390/0C (CU 3990/01) with 
300 cylinders, 15 heads, 224 sectors
[    2.241147] dasd-eckd.412b53: 0.0.0103: DASD with 4 KB/block, 216000 KB 
total size, 48 KB/track, compatible disk layout
[    2.245031]  dasdg:VOL1/  0X0103: dasdg1
[    2.250311] dasd-eckd.401b68: 0.0.8000: A channel path to the device has 
become operational
[    2.254957] dasd-eckd.2aa01a: 0.0.8000: New DASD 3390/0C (CU 3990/01) with 
3338 cylinders, 15 heads, 224 sectors
[    2.256328] dasd-eckd.412b53: 0.0.8000: DASD with 4 KB/block, 2403360 KB 
total size, 48 KB/track, compatible disk layout
[    2.263602]  dasdh:VOL1/  0X8006: dasdh1
[    2.272554] dasd-eckd.401b68: 0.0.8001: A channel path to the device has 
become operational
[    2.275070] dasd-eckd.2aa01a: 0.0.8001: New DASD 3390/0C (CU 3990/01) with 
500 cylinders, 15 heads, 224 sectors
[    2.277106] dasd-eckd.412b53: 0.0.8001: DASD with 4 KB/block, 360000 KB 
total size, 48 KB/track, compatible disk layout
[    2.285788]  dasdi:VOL1/  0X8001: dasdi1
[    2.311392] dasd-eckd.401b68: 0.0.8002: A channel path to the device has 
become operational
[    2.314520] dasd-eckd.2aa01a: 0.0.8002: New DASD 3390/0C (CU 3990/01) with 
140 cylinders, 15 heads, 224 sectors
[    2.319188] dasd-eckd.412b53: 0.0.8002: DASD with 4 KB/block, 100800 KB 
total size, 48 KB/track, compatible disk layout
[    2.324254]  dasdj:VOL1/  0X8002: dasdj1

-----Original Message-----
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Christian 
Borntraeger
Sent: Wednesday, August 10, 2016 10:44 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] vdisk swap in sles 12

On 08/10/2016 07:11 PM, Marcy Cortes wrote:
> Working on VDISK in sles 12.
> We've always just run a /etc/init.d/boot.local on sles 11 but I decided to 
> try it the cookbook way.
>
> I have 4 disks.
> Only FF00 and FF02 show up, but swapon -a later will bring the other 2 online.
>
> This is in /etc/fstab
> /dev/disk/by-path/ccw-0.0.ff00-part1 swap swap pri=4 0 0
> /dev/disk/by-path/ccw-0.0.ff01-part1 swap swap pri=3 0 0
> /dev/disk/by-path/ccw-0.0.ff02-part1 swap swap pri=2 0 0
> /dev/disk/by-path/ccw-0.0.ff03-part1 swap swap pri=1 0 0
>
> Right after boot
> zlnx169:~ # swapon
> NAME        TYPE        SIZE USED PRIO
> /dev/dasdd1 partition 976.6M   0B    2
> /dev/dasda1 partition 244.1M   0B    4
>
> They are OK, since swapon -a will bring them on zlnx169:~ # swapon -a 
> zlnx169:~ # swapon
> NAME        TYPE        SIZE USED PRIO
> /dev/dasdd1 partition 976.6M   0B    2
> /dev/dasda1 partition 244.1M   0B    4
> /dev/dasdc1 partition 488.3M   0B    3
> /dev/dasdf1 partition   1.9G   0B    1
>
>
> here are the relevant messages from journalctl
>
> Aug 10 11:55:32 zlnx169 systemd[1]: Found device 
> /dev/disk/by-path/ccw-0.0.ff02-part1.
> Aug 10 11:55:32 zlnx169 systemd[1]: Activating swap 
> /dev/disk/by-path/ccw-0.0.ff02-part1...
> Aug 10 11:55:32 zlnx169 systemd[1]: Starting LVM2 PV scan on device 94:33...
> Aug 10 11:55:32 zlnx169 systemd[1]: Starting LVM2 PV scan on device 94:37...
> Aug 10 11:55:32 zlnx169 systemd[1]: Found device 
> /dev/disk/by-path/ccw-0.0.ff03-part1.
> Aug 10 11:55:32 zlnx169 systemd[1]: Activating swap 
> /dev/disk/by-path/ccw-0.0.ff03-part1...
> Aug 10 11:55:32 zlnx169 systemd[1]: Starting LVM2 PV scan on device 94:25...
> Aug 10 11:55:32 zlnx169 swapon[3349]: swapon: /dev/dasdf1: read swap 
> header failed: Success Aug 10 11:55:32 zlnx169 kernel: Adding 999992k 
> swap on /dev/dasdd1.  Priority:2 extents:1 across:999992k Aug 10 
> 11:55:32 zlnx169 kernel: Adding 249992k swap on /dev/dasda1.  Priority:4 
> extents:1 across:249992k Aug 10 11:55:32 zlnx169 systemd[1]: Activated swap 
> /dev/disk/by-path/ccw-0.0.ff02-part1.
> Aug 10 11:55:32 zlnx169 systemd[1]: 
> dev-disk-by\x2dpath-ccw\x2d0.0.ff03\x2dpart1.swap swap process exited, 
> code=exited status=255 Aug 10 11:55:32 zlnx169 systemd[1]: Failed to activate 
> swap /dev/disk/by-path/ccw-0.0.ff03-part1.
> Aug 10 11:55:32 zlnx169 systemd[1]: Dependency failed for Swap.
> Aug 10 11:55:32 zlnx169 systemd[1]: Unit 
> dev-disk-by\x2dpath-ccw\x2d0.0.ff03\x2dpart1.swap entered failed state.
> Aug 10 11:55:32 zlnx169 systemd[1]: Found device 
> /dev/disk/by-path/ccw-0.0.ff00-part1.
> Aug 10 11:55:32 zlnx169 systemd[1]: Activating swap 
> /dev/disk/by-path/ccw-0.0.ff00-part1...
> Aug 10 11:55:32 zlnx169 systemd-sysctl[3366]: Overwriting earlier assignment 
> of kernel/sem in file '/etc/sysctl.d/99-sysctl.conf'.
> Aug 10 11:55:32 zlnx169 systemd[1]: Activated swap 
> /dev/disk/by-path/ccw-0.0.ff00-part1.
> Aug 10 11:55:32 zlnx169 systemd[1]: Starting LVM2 PV scan on device 94:17...
> Aug 10 11:55:32 zlnx169 systemd[1]: Starting LVM2 metadata daemon...
> Aug 10 11:55:32 zlnx169 systemd[1]: Started LVM2 metadata daemon.
> Aug 10 11:55:32 zlnx169 systemd-udevd[2006]: remove old symlink, 
> '/dev/disk/by-uuid/16795452-83d8-4b67-9a28-1e55947d9367' no longer belonging 
> to '/devices/cs Aug 10 11:55:32 zlnx169 systemd[1]: Found device 
> /dev/disk/by-path/ccw-0.0.ff01-part1.
> Aug 10 11:55:32 zlnx169 systemd[1]: Activating swap 
> /dev/disk/by-path/ccw-0.0.ff01-part1...
> Aug 10 11:55:32 zlnx169 systemd[1]: 
> dev-disk-by\x2dpath-ccw\x2d0.0.ff01\x2dpart1.swap swap process exited, 
> code=exited status=255 Aug 10 11:55:32 zlnx169 systemd[1]: Failed to activate 
> swap /dev/disk/by-path/ccw-0.0.ff01-part1.
> Aug 10 11:55:32 zlnx169 systemd[1]: Unit 
> dev-disk-by\x2dpath-ccw\x2d0.0.ff01\x2dpart1.swap entered failed state.
> Aug 10 11:55:32 zlnx169 swapon[3375]: swapon: 
> /dev/disk/by-path/ccw-0.0.ff01-part1: swapon failed: Invalid argument
>
> I may go back to the script.  But now I'm just too puzzled :)   How do i 
> figure out what a 255 is?

Is there a kernel message in "dmesg" ?

----------------------------------------------------------------------
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/

----------------------------------------------------------------------
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/

Reply via email to