I have add sda and sdb for our linux and multipath them(because they are
point to same LUN).
Then I logoff this linux guest and re-logon, everything is fine and we can
access new LUN disk space.
Then I use same method to add sdc and sdd for this linux and multipath them
(they are same LUN).
However, linux was booted abnormally, the whole startup message is
following. Any one know what cause it?
------------------------------------------------------------------------------------------------------------
DO YOU WANT TO IPL LINUX FROM MINIDISK 200? Y/N
y
00: zIPL v1.8.0-44.22.5 interactive boot menu
00:
00: 0. default (SLES11_SP1)
00:
00: 1. SLES11_SP1
00: 2. FailsafeV1
00: 3. ipl
00:
00: Note: VM users please use '#cp vi vmsg <number> <kernel-parameters>'
00:
00: Please choose (default will boot in 10 seconds):
00: Booting default (SLES11_SP1)...
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.32.12-0.7-default (geeko@buildhost) (gcc version 4.3.4
gcc-4_
3-branch revision 152973 (SUSE Linux) ) #1 SMP 2010-05-20 11:14:20 +0200
setup.1a06a7: Linux is running as a z/VM guest operating system in 64-bit
mode
Zone PFN ranges:
DMA 0x00000000 -> 0x00080000
Normal 0x00080000 -> 0x00080000
Movable zone start PFN for each node
early_node_map 2 active PFN ranges
0: 0x00000000 -> 0x00008800
0: 0x0000a200 -> 0x00041a00
PERCPU: Embedded 11 pages/cpu @0000000001a1e000 s12544 r8192 d24320 u65536
pcpu-alloc: s12544 r8192 d24320 u65536 alloc=16*4096
pcpu-alloc: 0 00 0 01 0 02 0 03 0 04 0 05 0 06 0 07
pcpu-alloc: 0 08 0 09 0 10 0 11 0 12 0 13 0 14 0 15
pcpu-alloc: 0 16 0 17 0 18 0 19 0 20 0 21 0 22 0 23
pcpu-alloc: 0 24 0 25 0 26 0 27 0 28 0 29 0 30 0 31
pcpu-alloc: 0 32 0 33 0 34 0 35 0 36 0 37 0 38 0 39
pcpu-alloc: 0 40 0 41 0 42 0 43 0 44 0 45 0 46 0 47 01:
HCPGSP26
27I The virtual machine is placed in CP mode due to a SIGP initial C
PU reset from CPU 00.
02: HCPGSP2627I The virtual machine is placed in CP mode due to a SIGP
initial C
PU reset from CPU 00.
03: HCPGSP2627I The virtual machine is placed in CP mode due to a SIGP
initial C
PU reset from CPU 00.
pcpu-alloc: 0 48 0 49 0 50 0 51 0 52 0 53 0 54 0 55
pcpu-alloc: 0 56 0 57 0 58 0 59 0 60 0 61 0 62 0 63
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 258469
Kernel command line: root=/dev/disk/by-path/ccw-0.0.0200-part1 TERM=dumb
BOOT_IM
AGE=0
PID hash table entries: 4096 (order: 3, 32768 bytes)
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Memory: 1011168k/1075200k available (4382k kernel code, 0k reserved, 2114k
data,
228k init)
Write protected kernel read-only data: 0x100000 - 0x5fffff
Hierarchical RCU implementation.
console ttyS0 enabled
allocated 13107200 bytes of page_cgroup
please try 'cgroup_disable=memory' option if you don't want memory cgroups
pid_max: default: 65536 minimum: 512
Security Framework initialized
AppArmor: AppArmor initialized
Mount-cache hash table entries: 256
Initializing cgroup subsys ns
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys net_cls
cpu.33a262: 4 configured CPUs, 0 standby CPUs
cpu.17772b: Processor 0 started, address 0, identification 02EF8D
cpu.17772b: Processor 1 started, address 0, identification 02EF8D
cpu.17772b: Processor 2 started, address 0, identification 02EF8D
cpu.17772b: Processor 3 started, address 0, identification 02EF8D
Brought up 4 CPUs
devtmpfs: initialized
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
AppArmor: AppArmor Filesystem Enabled
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
TCP established hash table entries: 65536 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
NET: Registered protocol family 1
Unpacking initramfs...
Freeing initrd memory: 5621k freed
audit: initializing netlink socket (disabled)
type=2000 audit(1315554916.548:1): initialized
HugeTLB registered 1 MB page size, pre-allocated 0 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
msgmni has been set to 496
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered (default)
io scheduler cfq registered
cio.b5d5f6: Channel measurement facility initialized using format extended
(mode
autodetected)
TCP cubic registered
registered taskstats version 1
Freeing unused kernel memory: 228k freed
doing fast boot
Creating device nodes with udev
udevd version 128 started
dasd-eckd.90fb0d: 0.0.0200: New DASD 3390/0A (CU 3990/01) with 3338
cylinders,
5 heads, 224 sectors
dasd-eckd.412b53: 0.0.0200: DASD with 4 KB/block, 2403360 KB total size, 48
KB/t
rack, compatible disk layout
dasda:VOL1/ 0X0200: dasda1
mount: devpts already mounted or /dev/pts busy
mount: according to mtab, devpts is already mounted on /dev/pts
Boot logging started on /dev/ttyS0(/dev/console) at Fri Sep 9 15:55:16
2011
kjournald starting. Commit interval 15 seconds
EXT3 FS on dasda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
resume device not found (ignoring)
Waiting for device /dev/disk/by-path/ccw-0.0.0200-part1 to appear: ok
fsck from util-linux-ng 2.16
/sbin/fsck.ext3 (1) -- / fsck.ext3 -a /dev/dasda1
/dev/dasda1: clean, 7643/150480 files, 118261/600816 blocks
fsck succeeded. Mounting root device read-write.
Mounting root /dev/disk/by-path/ccw-0.0.0200-part1
mount -o rw,acl,user_xattr -t
ext3 /dev/disk/by-path/ccw-0.0.0200-part1 /root
INIT: version 2.86 booting
System Boot Control: Running /etc/init.d/boot
Mounting sysfs at /sys..done
Mounting debugfs at /sys/kernel/debug..done
Copying static /dev content..done
Mounting devpts at /dev/pts..done
Boot logging started on /dev/ttyS0(/dev/console) at Fri Sep 9 07:55:43
2011
udevd version 128 started
dasd-eckd.90fb0d: 0.0.0202: New DASD 3390/0A (CU 3990/01) with 3338
cylinders, 1
5 heads, 224 sectors
dasd-eckd.90fb0d: 0.0.0201: New DASD 3390/0A (CU 3990/01) with 3338
cylinders, 1
5 heads, 224 sectors
dasd-eckd.90fb0d: 0.0.0203: New DASD 3390/0A (CU 3990/01) with 3338
cylinders, 1
5 heads, 224 sectors
dasd-eckd.412b53: 0.0.0201: DASD with 4 KB/block, 2403360 KB total size, 48
KB/t
rack, compatible disk layout
dasde:VOL1/ 0X0201: dasde1
dasd-eckd.412b53: 0.0.0203: DASD with 4 KB/block, 2403360 KB total size, 48
KB/t
rack, compatible disk layout
dasdc:
dasd-eckd.90fb0d: 0.0.0204: New DASD 3390/0A (CU 3990/01) with 3338
cylinders, 1
5 heads, 224 sectors
VOL1/ 0X0203:
dasd-eckd.412b53: 0.0.0204: DASD with 4 KB/block, 2403360 KB total size, 48
KB/t
rack, compatible disk layout
dasdb: dasdc1
VOL1/ 0X0204:
dasd-eckd.90fb0d: 0.0.0205: New DASD 3390/0A (CU 3990/01) with 3338
cylinders, 1
5 heads, 224 sectors
dasd-eckd.412b53: 0.0.0205: DASD with 4 KB/block, 2403360 KB total size, 48
KB/t
rack, compatible disk layout
dasdf:
SCSI subsystem initialized
dasd-eckd.412b53: 0.0.0202: DASD with 4 KB/block, 2403360 KB total size, 48
KB/t
rack, compatible disk layout
dasdd:VOL1/ 0X0205:
VOL1/ 0X0202: dasdd1
vmur.c793e5: z/VM virtual unit record device driver loaded.
dasd-eckd.90fb0d: 0.0.0206: New DASD 3390/0A (CU 3990/01) with 3338
cylinders, 1
5 heads, 224 sectors
dasd-eckd.412b53: 0.0.0206: DASD with 4 KB/block, 2403360 KB total size, 48
KB/t
rack, compatible disk layout
dasdg:VOL1/ 0X0206:
qeth.87067b: loading core functions
dasd-fba.757950: 0.0.0300: New FBA DASD 9336/10 (CU 6310/80) with 256 MB
and 512
B/blk
dasdh:CMS1/ LXSWAP(MDSK): dasdh1
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
qeth.2c6def: register layer 3 discipline
qdio: 0.0.0602 OSA on SC 2 using AI:1 QEBSM:0 PCI:1 TDD:1 SIGA:RW AO
qdio: 0.0.0612 HS on SC 5 using AI:1 QEBSM:0 PCI:0 TDD:1 SIGA: W AO
qeth.736dae: 0.0.0600: Device is a Guest LAN QDIO card (level: V543)
with link type GuestLAN QDIO (portname: )
qeth.47953b: 0.0.0600: Hardware IP fragmentation not supported on eth0
qeth.066069: 0.0.0600: Inbound source MAC-address not supported on eth0
qeth.d7fdb4: 0.0.0600: VLAN enabled
qeth.e90c78: 0.0.0600: Multicast enabled
qeth.5a9d02: 0.0.0600: IPV6 enabled
qeth.184d8a: 0.0.0600: Broadcast enabled
qeth.dac2aa: 0.0.0600: Using SW checksumming on eth0.
qeth.9c4c89: 0.0.0600: Outbound TSO not supported on eth0
qdio: 0.0.7002 HS on SC 8 using AI:1 QEBSM:1 PCI:0 TDD:1 SIGA: W AO
qeth.26d434: 0.0.0610: Device is a Guest LAN Hiper card (level: V543)
with link type GuestLAN Hiper.
scsi0 : zfcp
qeth.47953b: 0.0.0610: Hardware IP fragmentation not supported on hsi0
qeth.066069: 0.0.0610: Inbound source MAC-address not supported on hsi0
qeth.d7fdb4: 0.0.0610: VLAN enabled
qdio: 0.0.3300 ZFCP on SC 9 using AI:1 QEBSM:1 PCI:1 TDD:1 SIGA: W AO
qeth.e90c78: 0.0.0610: Multicast enabled
qeth.5a9d02: 0.0.0610: IPV6 enabled
qeth.184d8a: 0.0.0610: Broadcast enabled
qeth.dac2aa: 0.0.0610: Using SW checksumming on hsi0.
qeth.9c4c89: 0.0.0610: Outbound TSO not supported on hsi0
qeth.26d434: 0.0.7000: Device is a HiperSockets card (level: D60M)
with link type HiperSockets.
qeth.5ffaa1: 0.0.7000: set adapter parameters not supported.
qeth.47953b: 0.0.7000: Hardware IP fragmentation not supported on hsi1
qeth.066069: 0.0.7000: Inbound source MAC-address not supported on hsi1
qeth.d7fdb4: 0.0.7000: VLAN enabled
qeth.e90c78: 0.0.7000: Multicast enabled
qeth.5a9d02: 0.0.7000: IPV6 enabled
qeth.184d8a: 0.0.7000: Broadcast enabled
qeth.dac2aa: 0.0.7000: Using SW checksumming on hsi1.
qeth.9c4c89: 0.0.7000: Outbound TSO not supported on hsi1
scsi 0:0:0:1073758208: Direct-Access IBM 2107900 3.44 PQ:
0 AN
SI: 5
scsi1 : zfcp
qdio: 0.0.3306 ZFCP on SC b using AI:1 QEBSM:1 PCI:1 TDD:1 SIGA: W AO
sd 0:0:0:1073758208: sda 1656750080 512-byte logical blocks: (848 GB/790
GiB)
sd 0:0:0:1073758208: sda Write Protect is off
sd 0:0:0:1073758208: sda Write cache: enabled, read cache: enabled,
doesn't su
pport DPO or FUA
sda: sda1
sd 0:0:0:1073758208: sda Attached SCSI disk
sd 0:0:0:1073758208: Attached scsi generic sg0 type 0
scsi 1:0:0:1073823744: Direct-Access IBM 2107900 3.44 PQ:
0 AN
SI: 5
sd 1:0:0:1073823744: Attached scsi generic sg1 type 0
scsi2 : zfcp
qdio: 0.0.3f00 ZFCP on SC a using AI:1 QEBSM:1 PCI:1 TDD:1 SIGA: W AO
sd 1:0:0:1073823744: sdb 1656750080 512-byte logical blocks: (848 GB/790
GiB)
sd 1:0:0:1073823744: sdb Write Protect is off
sd 1:0:0:1073823744: sdb Write cache: enabled, read cache: enabled,
doesn't su
pport DPO or FUA
sdb: sdb1
sd 1:0:0:1073823744: sdb Attached SCSI disk
scsi3 : zfcp
scsi 2:0:0:1073758208: Direct-Access IBM 2107900 3.44 PQ:
0 AN
SI: 5
sd 2:0:0:1073758208: Attached scsi generic sg2 type 0
qdio: 0.0.3f06 ZFCP on SC c using AI:1 QEBSM:1 PCI:1 TDD:1 SIGA: W AO
sd 2:0:0:1073758208: sdc 1656750080 512-byte logical blocks: (848 GB/790
GiB)
sd 2:0:0:1073758208: sdc Write Protect is off
sd 2:0:0:1073758208: sdc Write cache: enabled, read cache: enabled,
doesn't su
pport DPO or FUA
sdc: sdc1
sd 2:0:0:1073758208: sdc Attached SCSI disk
scsi 3:0:0:1073823744: Direct-Access IBM 2107900 3.44 PQ:
0 AN
SI: 5
sd 3:0:0:1073823744: Attached scsi generic sg3 type 0
sd 3:0:0:1073823744: sdd 1656750080 512-byte logical blocks: (848 GB/790
GiB)
sd 3:0:0:1073823744: sdd Write Protect is off
sd 3:0:0:1073823744: sdd Write cache: enabled, read cache: enabled,
doesn't su
pport DPO or FUA
sdd: sdd1
sd 3:0:0:1073823744: sdd Attached SCSI disk
Adding 259956k swap on /dev/dasdh1. Priority:-1 extents:1 across:259956k
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised:
[email protected]
device-mapper: multipath: version 1.1.0 loaded
device-mapper: multipath round-robin: version 1.0.0 loaded
blogd: no message logging because /var file system is not accessible
Starting udevd: ..done
Loading drivers, configuring devices: ..done
Activating swap-devices in /etc/fstab...
..doneSetting up the System Clock..done
..done
Activating device mapper...
..done
Loading required kernel modules
..doneCreating multipath targets:..done
Waiting for /dev/mapper/36005076308ffc6210000000000000000_part1 . no more
events
Checking file systems...
fsck from util-linux-ng 2.16
Checking all file systems.
/sbin/fsck.ext3 (1) -- /usr fsck.ext3 -a /dev/dasde1
/dev/dasde1: clean, 59281/150480 files, 495837/600816 blocks
/sbin/fsck.ext3 (1) -- /usr/share fsck.ext3 -a /dev/dasdd1
/dev/dasdd1: clean, 86799/150480 files, 362694/600816 blocks
/sbin/fsck.ext3 (1) -- /var fsck.ext3 -a /dev/dasdc1
/dev/dasdc1: clean, 2079/150480 files, 61636/600816 blocks
/sbin/fsck.ext3 (1) -- /vol2 fsck.ext3
-a /dev/mapper/36005076308ffc6210000000
000000001_part1
/dev/mapper/36005076308ffc6210000000000000001_part1: clean, 12/51773440
files,
299738/207091899 blocks
/sbin/fsck.ext3 (1) -- /vol1 fsck.ext3
-a /dev/mapper/36005076308ffc6210000000
000000000_part1
fsck.ext3: No such file or directory while trying to
open /dev/mapper/3600507630
8ffc6210000000000000000_part1
/dev/mapper/36005076308ffc6210000000000000000_part1:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
..failed
fsck failed for at least one filesystem (not /).
Please repair manually and reboot.
The root file system is is already mounted read-write.
Attention: Only CONTROL-D will reboot the system in this
maintanance mode. shutdown or reboot will not work.
Give root password for login:
------------------------------------------------------------------------------------
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] 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/
