RAID problem

[Andrzej Krzysztofowicz]

Ma ktos pomysl, w jaki sposob zrobic RAID odporny na tasowanie dyskami?
Bo mam z tym problem. Zrobilem taki test: wyrejestrowalem dwa dyski i
zarejestrowalem je w odwrotnej kolejnosci:  sdg <--> sdh. Oto efekt:

mdadm: looking for devices for /dev/md1
mdadm: /dev/sdh1 is identified as a member of /dev/md1, slot 4.
mdadm: no RAID superblock on /dev/sdg1
mdadm: /dev/sdg1 has wrong uuid.
mdadm: /dev/sdf1 has wrong uuid.
mdadm: /dev/sde1 is identified as a member of /dev/md1, slot 3.
mdadm: /dev/sdd1 is identified as a member of /dev/md1, slot 2.
mdadm: /dev/sdc1 is identified as a member of /dev/md1, slot 1.
mdadm: /dev/sdb1 has wrong uuid.
mdadm: /dev/hda1 is identified as a member of /dev/md1, slot 0.

Znalazl wszystkie 5 dyskow wchodzacych w sklad. Ale kernel w dmesgu pisze:

(read) [dev 03:01]'s sb offset: 19534912 [events: 0000000c]
(read) sdc1's sb offset: 8844160 [events: 0000000c]
(read) sdd1's sb offset: 2097024 [events: 0000000c]
(read) sde1's sb offset: 2097024 [events: 0000000c]
(read) sdg1's sb offset: 8192448 [events: 6c6c6c6c]

[ Dlaczego sdg1 ??? ]

md: invalid raid superblock magic on sdg1

[ nic dziwnego ]

md: sdg1 has invalid sb, not importing!
could not import sdg1, trying to run array nevertheless.

[ i nie zadziala, bo to nie jest RAID5 tylko RAID1 ]

autorun ...
considering sde1 ...
...

Any idea ?
Aha, kernel 2.2 z Ra.

A tasowania dyskow raczej sie nie da uniknac, bo sa one wpiete do kilku
kontrolerow i nigdy nie wiadomo, na ktorym przyjdzie robic zmiany.

-- 
=======================================================================
  Andrzej M. Krzysztofowicz               ankry w mif.pg.gda.pl
  phone (48)(58) 347 14 61
Faculty of Applied Phys. & Math.,   Gdansk University of Technology