Re: patch fr1-2.17 does not work with kernel 2.4.30

"Also sprach Stephan von Krawczynski:"
> I re-did the test according to FR1 readme with raidsetfaulty / raidhotadd and
> found out it resyncs the whole raid although there should be no difference
> between the two devices "out of sync".
> I have no good idea where to look for this problem. Can you point somewhere?

I have now been able to check, and hotrepair works here (2.4.30,
patched with UML 2.4.27).

sh-2.03# mdadm -C -l 1 -n 2 -x 0 /dev/md/0 /dev/ubd[12]
mdadm: You haven't given enough devices (real or missing) to create
this array
sh-2.03# mdadm -C -l 1 -n 2 -x 0 /dev/md/0 /dev/ubd/[12]
mdadm: array /dev/md/0 started.
sh-2.03# cat /proc/mdstat 
Personalities : [raid1] 
read_ahead 1024 sectors
md0 : active raid1 ubd/disc2/disc[1] ubd/disc1/disc[0]
      4032 blocks [2/2] [UU]
      
unused devices: <none>
sh-2.03# sync
sh-2.03# raidsetfaulty /dev/md/0 /dev/ubd/2
sh-2.03# echo hi > /dev/md/0
sh-2.03# sync
sh-2.03# raidhotadd /dev/md/0 /dev/ubd/2
sh-2.03# 

And the kernel shows:

md: syncing RAID array md0
md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc.
md: using maximum available idle IO bandwith (but not more than 100000
KB/sec) for reconstruction.
md: using 124k window, over a total of 4032 blocks.
md0: retained bitmap a027dc60
raid1: synced dirty sectors 0-7

# raid1: skipped clean sectors 8-8063
md: md0: sync done.


So it looks correct (I have not tried with SMP).

Peter