Redhat 8.0 & RAID

Page principale

Répondre à ce message
Auteur: Philippe B
Date:  
À: guilde
Sujet: Redhat 8.0 & RAID
Bonjour,

j'ai un gros soucis sur une machine équipée de RAID. Voici la configuration
:

/dev/md0 on / type ext3 (rw)
none on /proc type proc (rw)
usbdevfs on /proc/bus/usb type usbdevfs (rw)
/dev/hda1 on /boot type ext3 (rw)
/dev/hdb3 on /boot-bck type ext3 (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/md1 on /home type ext3 (rw,usrquota)
none on /dev/shm type tmpfs (rw)

/dev/md0 / ext3 rw 0 0
none /proc proc rw 0 0
usbdevfs /proc/bus/usb usbdevfs rw 0 0
/dev/hda1 /boot ext3 rw 0 0
/dev/hdb3 /boot-bck ext3 rw 0 0
none /dev/pts devpts rw,gid=5,mode=620 0 0
/dev/md1 /home ext3 rw,usrquota 0 0
none /dev/shm tmpfs rw 0 0

En gros, le RAID est géré logiciellement par la redhat sur 2 disques
séparés.
Dès qu'un crash se produit, la machine mets des heures à se relancer ...

Voici un extrait du /var/log/messages :

md: raid1 personality registered as nr 3
Journalled Block Device driver loaded
md: Autodetecting RAID arrays.
[events: 00000016]
[events: 00000016]
[events: 00000016]
[events: 00000016]
md: autorun ...
md: considering hda2 ...
md: adding hda2 ...
md: adding hdb1 ...
md: created md1
md: bind<hdb1,1>
md: bind<hda2,2>
md: running: <hda2><hdb1>
md: hda2's event counter: 00000016
md: hdb1's event counter: 00000016
md: md1: raid array is not clean -- starting background reconstruction
md: RAID level 1 does not need chunksize! Continuing anyway.
md1: max total readahead window set to 508k
md1: 1 data-disks, max readahead per data-disk: 508k
raid1: device hda2 operational as mirror 0
raid1: device hdb1 operational as mirror 1
raid1: raid set md1 not clean; reconstructing mirrors
raid1: raid set md1 active with 2 out of 2 mirrors
md: updating md1 RAID superblock on device
md: hda2 [events: 00000017]<6>(write) hda2's sb offset: 66766016
md: syncing RAID array md1
md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc.
md: using maximum available idle IO bandwith (but not more than 10000
KB/sec) fo
r reconstruction.
md: using 508k window, over a total of 66766016 blocks.
md: hdb1 [events: 00000017]<6>(write) hdb1's sb offset: 66766016
md: considering hda3 ...
md: adding hda3 ...
md: adding hdb2 ...
md: created md0
md: bind<hdb2,1>
md: bind<hda3,2>
md: running: <hda3><hdb2>
md: hda3's event counter: 00000016
md: hdb2's event counter: 00000016
md: md0: raid array is not clean -- starting background reconstruction
md: RAID level 1 does not need chunksize! Continuing anyway.
md0: max total readahead window set to 508k
md0: 1 data-disks, max readahead per data-disk: 508k
raid1: device hda3 operational as mirror 0
raid1: device hdb2 operational as mirror 1
raid1: raid set md0 not clean; reconstructing mirrors
raid1: raid set md0 active with 2 out of 2 mirrors
md: updating md0 RAID superblock on device
md: hda3 [events: 00000017]<6>(write) hda3's sb offset: 10241344
md: delaying resync of md0 until md1 has finished resync (they share one or
more
physical units)
spurious 8259A interrupt: IRQ7.
md: hdb2 [events: 00000017]<6>(write) hdb2's sb offset: 10241344
md: ... autorun DONE.

Si quelqu'un aurait une idée ca m'aiderait beaucoup ..
étant donné qu'il y a deja un souci apache sur cette machine (et que c'est
pas evident à analyser !!)

Philippe