[Bugme-janitors] [Bug 6965] Kernel doesn't re-sync usb-raid1 after running mdadm --add

[bugme-daemon at bugzilla.kernel.org]

http://bugzilla.kernel.org/show_bug.cgi?id=6965





------- Additional Comments From neilb at suse.de  2006-08-06 01:52 -------
On Sunday August 6, bugme-daemon at bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=6965
> 
>            Summary: Kernel doesn't re-sync usb-raid1 after running mdadm --
>                     add
>     Kernel Version: 2.6.18-rc3
> 
> Most recent kernel where this bug did not occur: 2.6.18-rc2

This is very surprising as
   git log v2.6.18-rc2..v2.6.18-rc3 drivers/md/
doesn't list anything.  i.e. there have been no
relevant changes in that time.

There was a change leading up to rc1 that could 
possibly explain the situation. 
 commit 07d84d109d8beedd68df9da2e4e9f25c8217e7fb

If you add a drive to an array, and that drive was previously
part of the array, and no actual writes have happened in the
mean time, then the array will be added with no resync (which
is probably what you want).

It could be that the change t master.pid has not actually
been flushed to disk at the time when you break the array
and remount the usb drive.

Could you try the same experiment, only give the command
  sync ; sync
before failing and removing /dev/hda3 ?
Let me know what happens.

Thanks,
NeilBrown



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.