linux-kernel - Re: [bug?] raid1 integrity checking is broken on 2.6.18-rc4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <17650.26437.447617.467168@cse.unsw.edu.au>
Date:	Mon, 28 Aug 2006 13:47:17 +1000
From:	Neil Brown <neilb@...e.de>
To:	Chuck Ebbert <76306.1226@...puserve.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-raid <linux-raid@...r.kernel.org>
Subject: Re: [bug?] raid1 integrity checking is broken on 2.6.18-rc4

On Thursday August 17, 76306.1226@...puserve.com wrote:
> 
> I just tried the patch and now it seems to be syncing the drives instead
> of only checking them?  (At the very least the message is misleading.)
> 

Yes, the message is misleading.  I should fix that.

NeilBrown


>  # echo "check" >/sys/block/md0/md/sync_action
>  # dmesg | tail -9
>  md: syncing RAID array md0
>  md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
>  md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction.
>  md: using 128k window, over a total of 104256 blocks.
>  md: md0: sync done.
>  RAID1 conf printout:
>   --- wd:2 rd:2
>   disk 0, wo:0, o:1, dev:hda9
>   disk 1, wo:0, o:1, dev:sda5
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/