Uhm... Martin I would strongly warn you from setting a dasd that is part 
of a
mirroring md device online on a different system. 
- In case the original system is active at that time you will run into 
consistency trouble 
  because of multiple mounts without using a shared filesystem
- even when the original system is down, Zipl will create files on your 
dasd (bootmap
  for example), and they are _not_ the same as on the mirror copy. Your 
mirror consistency 
  is broken when you do this. 

I do strongly recommend using seperate dasd on /boot, no md device there!

with kind regards
Carsten Otte
-- 
I saw screens of green, red messages too, then came blue, shubidu
And i think to myself, what a wonderful world




Lufthansa Systems Infratec ZLINUX SYSPROG <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
13/08/2004 12:22 PM
Please respond to Linux on 390 Port

 
        To:     [EMAIL PROTECTED]
        cc: 
        Subject:        Re: raid1

 

Hi Carsten,

Hm, but it works perfect - without having a /boot on a plain dasd or 
scsi-disk. 
We boot from /dev/md0. ok, you can not make a "zipl" on a /dev/md0. but 
that's not necessary. Just mount the dasd on a second linux and then use 
zipl to write the boot-data. 
I only created a special initrd. Made a "mkraid" with a new dasd and copy 
a linux-installation on it. If you add a mirror to the system, you have to 
remember that there is no boot-information on it. Ergo - before you able 
to boot from an new mirror-device mount the dasd on a second system and do 
a "zipl". Sad, that zipl is not able to see the ucb/dasd behind a 
md-device to write the boot-record. 
 

Lufthansa Systems Infratec GmbH

Martin Lonkwitz                             Lufthansa Systems GmbH
UNIX Systems Engineer      FRA AR/ISS
Systemplanung,-betrieb     Am Weiher 24
und Entwicklung            D-65451 Kelsterbach
                           Telefon:(069) 696-72456
Externer Servicepartner der Firma 
networker, projektberatung GmbH 
Am Kaltenborn 1 
61462 K�nigstein 

 

 

 

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of 
Carsten Otte
Sent: Freitag, 13. August 2004 10:21
To: [EMAIL PROTECTED]
Subject: Re: raid1

Hi Martin,

you cannot use a raid1 device for boot itself. The zipl bootloader 
requires either a scsi disk or a dasd. With SLES this means, that you need 
to have a plain dasd mounted on /boot in order to ipl.
For the root filesystem you can in fact use raid1 via the md driver or via 
the logical volume manager. In case you are looking for full redundancy of 
storage devices, it seems wise to create a second copy of the /boot 
filesystem, and run zipl on the second ipl device as well. You will then 
be able to boot from either disk, but you need to remember to re-do the 
procedure whenever you update your system kernel.

with kind regards
Carsten Otte
--
I saw screens of green, red messages too, then came blue, shubidu And i 
think to myself, what a wonderful world




Lufthansa Systems Infratec ZLINUX SYSPROG <[EMAIL PROTECTED]> Sent 
by: Linux on 390 Port <[EMAIL PROTECTED]>
13/08/2004 08:01 AM
Please respond to Linux on 390 Port


        To:     [EMAIL PROTECTED]
        cc:
        Subject:        raid1



Hi list !

Is anyone using raid1 as a boot-device under Suse SLES 8 or 9 ? if so, 
what's your experience ?

cu
martin


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

Reply via email to