Re: Re: fr1-2.16 patch for 2.6.10 kernel

denis bonnenfant <[email protected]>
Newsgroups gmane.linux.enbd.general
Message-ID <[email protected]>
> 
> Can you replace:
> 
> #ifdef MD_BITMAP_SUPPORT
>         /* get the component's superblock */
> +       read_disk_sb(rdev);
>         sb = (mdp_super_t *)page_address(rdev->sb_page);
> 
> 
> (untested - you are guinea pig).
> 
> It looks as though one can skip that if rdev->sb_page is non-null and
> if rdev->sb_loaded is nonzero. But try that first.

It's better. fast resync 5-6 times successivly, but now,

.....
md0: repair bit set on sb so retained bitmap f7ff4bc0
raid1: skipped clean sectors 0-979711
md: md0: sync done.
RAID1 conf printout:
  --- wd:2 rd:2
  disk 0, wo:0, o:1, dev:sda1
  disk 1, wo:0, o:1, dev:sdb1
md0: md_check_recovery 1: repair bit 0 on sb f7fc8480 preserved
md0: md_check_recovery 2: repair bit 0 on sb f7fc8480 preserved
XFS mounting filesystem md0
Ending clean XFS mount for filesystem: md0
raid1: Disk failure on sda1, disabling device.
         Operation continuing on 1 devices
raid1: bitmap f7ff4bc0 already active!
md0: md_check_recovery 2: repair bit 0 on sb f7fc8480 preserved
md: trying to hot-add unknown-block(8,1) to md0 ...
md0: repair of faulty disk 800001!
md: trying to remove unknown-block(8,1) from md0 ...
md0: notifying dev 800001 it is no longer in array
md: unbind<sda1>
md: export_rdev(sda1)
md 1205: unlock_rdev nulls bdev
md 1197: lock_rdev restores bdev 800001
sda1 (read) [events: 000000e6]
md: *** lecture uuid  800001
md: old uuid 5dc1267b 788f7499 cd49d3c0 d06f0b96
md: new uuid 5dc1267b 788f7499 cd49d3c0 d06f0b96
md0: new disk 800001 too old for repair (disk 230 < bitmap 232)  <****** 
still a problem ?

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: repair bit 0 on sb f7fc8480 preserved

it occurs just one time, and now it's ok again.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.