Re: Re: fr1-2.16 patch for 2.6.10 kernel

A second cycle, a little bit different !

raid1: Disk failure on sda1, disabling device.
         Operation continuing on 1 devices
raid1: bitmap f7cbb740 already active!
md0: md_check_recovery 2: cleared recovery bits on sb f7fc8480
md: 3830
md: 3838
md: 3846
md: 3838
md: 3846
md 3875: ** mddev=f7fc8480 rdev=f71d92c0
md 3882: ** mddev=f7fc8480 rdev=f71d92c0
md 3875: ** mddev=f7fc8480 rdev=f7ff7c80
md 3882: ** mddev=f7fc8480 rdev=f7ff7c80
md 3875: ** mddev=f7fc8480 rdev=f7fc8490
md 3897: ** mddev=f7fc8480 rdev=f7fc8490
md: 3863
md: unlock at line 3891
md 2361: ** mddev=f7fc8480
md: trying to hot-add unknown-block(8,1) to md0 ...
md 2387: ** mddev=f7fc8480 rdev=f71d92c0
md0: repair of faulty disk 800001!
md: trying to remove unknown-block(8,1) from md0 ...

maybe here in hot_remove_disk() ?

md0: notifying dev 800001 it is no longer in array
md: unbind<sda1>
md: export_rdev(sda1)
md 2421: ** rdev=f71d9580
md: adding new mirror component 800001
md: old uuid c03e31b8 d7052438 5d266bb8 5d8cbf97
md: new uuid 0 4011 624f2037 7463656a

why does it detects the disk as a new one this time ?

        } else {
                 /* failed match */
                 hotrepair = 0;

It seems that sb has not been read correctly, as the the disk has not been changed since last fail.

md0: WARNING: sda1 appears to be on the same physical disk as sda2. True
      protection against single-disk failure might be compromised.
md: bind<sda1>
md0: notifying dev 800001 it is now in array
md0: set repair bit to 0 on superblock f7fc8480
md0: md_check_recovery 2: cleared recovery bits on sb f7fc8480
md: 3830
md: 3838
md: 3846
md: 3838
md: 3846
md 3875: ** mddev=f7fc8480 rdev=f71d9580
md 3882: ** mddev=f7fc8480 rdev=f71d9580
md 3884: ** mddev=f7fc8480 rdev=f71d9580
md 3885: ** mddev->pers=f88a8b60
md 3886: ** mddev->pers->hot_add_disk=f88a5388
Unable to handle kernel NULL pointer dereference at virtual address 00000004
  printing eip:
f88a53d7