Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Linux as VIO Client LPAR ( bonding,raid Problems)

Status
Not open for further replies.

AIX5L

Technical User
Jul 27, 2001
228
0
0
CH
Hi

Has anybody experience with RHEL 4.0 and SLES 9.0 on P5 ?
I have Problems with the bonding Device with 2 VIO Servers to bring up the Interfaces in the arp Monitoring Mode.

What is the best way to resync/recreate the Linux RAID1 Mirror when 1 Mirror( VIO-Server ) will go down ?

Even i reboot one VIO-Server my Raid looks like this:

md2 : active raid1 sdb1[0]
10485632 blocks [2/1] [U_]
where is sdd1 ?
md1 : active raid1 sdc4[1]
9825216 blocks [2/1] [_U]
where is sda4 ?

md0 : inactive
unused devices: <none>

Why is my md0 inavtive ( swap ) ?
/dev/sda3 and /dev/sdc3


linux:/data # fdisk -l /dev/sda

Disk /dev/sda: 10.7 GB, 10737418240 bytes
64 heads, 32 sectors/track, 10240 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 11 11248 6 FAT16
/dev/sda2 12 132 123904 83 Linux
/dev/sda3 133 645 525312 fd Linux raid autodetect
/dev/sda4 646 10240 9825280 fd Linux raid autodetect


linux:/data # fdisk -l /dev/sdc

Disk /dev/sdc: 10.7 GB, 10737418240 bytes
64 heads, 32 sectors/track, 10240 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 1 11 11248 41 PPC PReP Boot
/dev/sdc2 12 132 123904 83 Linux
/dev/sdc3 133 645 525312 fd Linux raid autodetect
/dev/sdc4 646 10240 9825280 fd Linux raid autodetect


sda is on vio1
sdc is on vio2
both are SAN Disks direct attached over vscsi ( no lv )

If i reboot my LPAR:

dmesg:

SCSI error : <0 0 1 0> return code = 0x6000000
end_request: I/O error, dev sda, sector 20971472
Buffer I/O error on device sda4, logical block 2456314
md: could not lock sda4.
md: error, md_import_device() returned -16
md: raidstart(pid 986) used deprecated START_ARRAY ioctl. This will not be supported beyond 2.6
md: could not lock sda4.
md: could not import sda4!
device-mapper: 4.3.0-ioctl (2004-09-30) initialised: dm-devel@redhat.com
md: autostart unknown-block(0,2052) failed!
md: Autodetecting RAID arrays.
md: could not lock sda4.
md: could not import sda4!
md: autorun ...
md: considering sdd1 ...
md: adding sdd1 ...
md: sdc4 has different UUID to sdd1
md: sdc3 has different UUID to sdd1
md: adding sdb1 ...
md: sda3 has different UUID to sdd1
md: created md2
md: bind<sdb1>
md: bind<sdd1>
md: running: <sdd1><sdb1>
md: kicking non-fresh sdd1 from array!
md: unbind<sdd1>
md: export_rdev(sdd1)
md: raid1 personality registered as nr 3
raid1: raid set md2 active with 1 out of 2 mirrors
md: considering sdc4 ...
md: adding sdc4 ...
md: sdc3 has different UUID to sdc4
md: sda3 has different UUID to sdc4
md: created md1
md: bind<sdc4>
md: running: <sdc4>
raid1: raid set md1 active with 1 out of 2 mirrors
md: considering sdc3 ...
md: adding sdc3 ...
md: adding sda3 ...
md: md0 already running, cannot run sdc3
md: export_rdev(sda3)
md: export_rdev(sdc3)
md: ... autorun DONE.

 
Hi

Is there nobody with Experience on Virutalization ?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top