I had a similar experience and got around it using:
ckraid --force-check --fix /dev/md0
I attributed to immature software that errs on the side of caution...
If I recall I had a similar situation with ext2 in the early days.
On Tue, 6 Apr 1999, Linux SMP Mlist wrote:
> Hi,
>
> i have /dev/sda3 a /dev/sdb3 in RAID1 array.
>
> I've run raidadd /dev/md0, raidrun /dev/md0 - OK.
> mount /dev/md0 - OK
> raidstop /dev/md0 - OK
>
> mount /dev/sda3 /mnt/ OK
> umount /mnt OK
>
> Now i've tried to start raid device but ...
> raidadd /dev/md0 OK
> raidrun /dev/md0 - > "raid1: detected mirror differences -- run ckraid"
>
> ckraid /dev/md0 (i've tried all combinations of params)
> ckraid:
> analyzing superblock
> disk 0: /dev/sda3, 2048287kB, raid superblock at 2048192kB
> disk 1: /dev/sdb3, 2048287kB, raid superblock at 2048192kB
> reading superblock
> device /dev/md0 already clean, not checking
> ckraid: completed
>
> How is it possible ?????????????
> ckraid said "OK", but raidrun said "error"
>
> Thanks for an answer
>
> JD
> --
> ,{(~)~(}, Dadak Jakub Brain Systems s.r.o.
> ,( ((~) ){){} [EMAIL PROTECTED] Rybkova 1
> ())~{)}{{}~()} http://www.brainsys.cz Brno 602 00
> `~^ ^~{()} Tel. +420 5 41148704 Fax. +420 5 41148852
> ~~ Motto: Things are different !
>
--
Erich
http://cr808276-a.ktchnr1.on.wave.home.com
Microsoft is to software what McDonalds is to gourmet cooking;
