linux user group brescia

Ciao a tutti,

una curiosita' (ammetto di essere ignorante sui raid software, Angrea G. sii
paziente cone me :-)

a parte un disk failure, o uno spegnimento "azzardato", quali possono essere
le cause che forzano una risincronizzazione del raid ?

Posso vedere i seguenti :

cat /proc/mdstat

Personalities : [raid1]
read_ahead 1024 sectors
md0 : active raid1 hdc1[1] hda1[0] 24576 blocks [2/2] [UU] resync=DELAYED
md1 : active raid1 hdc5[1] hda5[0] 2097536 blocks [2/2] [UU] resync=DELAYED
md2 : active raid1 hdc6[1] hda6[0] 2097536 blocks [2/2] [UU] resync=DELAYED
md3 : active raid1 hdc7[1] hda7[0] 1048704 blocks [2/2] [UU] resync=DELAYED
md4 : active raid1 hdc8[1] hda8[0] 14498560 blocks [2/2] [UU] resync=7%
finish=1
49.4min
unused devices: <none>


e dal /var/log/messages ....

...
...
May 18 17:14:08 golem kernel: created md2
May 18 17:14:08 golem kernel: bind<hda6,1>
May 18 17:14:08 golem kernel: bind<hdc6,2>
May 18 17:14:08 golem kernel: running: <hdc6><hda6>
May 18 17:14:08 golem kernel: now!
May 18 17:14:08 golem kernel: hdc6's event counter: 00000045
May 18 17:14:08 golem kernel: hda6's event counter: 00000045
May 18 17:14:08 golem kernel: md: md2: raid array is not clean -- starting
backg
round reconstruction
May 18 17:14:08 golem kernel: md2: max total readahead window set to 128k
May 18 17:14:08 golem kernel: md2: 1 data-disks, max readahead per
data-disk: 12
8k
May 18 17:14:08 golem kernel: raid1: device hdc6 operational as mirror 1
May 18 17:14:08 golem kernel: raid1: device hda6 operational as mirror 0
May 18 17:14:08 golem kernel: raid1: raid set md2 not clean; reconstructing
mirr
ors
May 18 17:14:08 golem kernel: raid1: raid set md2 active with 2 out of 2
mirrors
May 18 17:14:08 golem kernel: md: updating md2 RAID superblock on device
May 18 17:14:08 golem kernel: hdc6 [events: 00000046](write) hdc6's sb
offset:
...
...


I dischi sembrano funzionare ancora tutti e due correttamente.

Grazie, Alfredo.