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/

Reply via email to